From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Pete Clements <clem@clem.clem-digital.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16-git12 killed networking -- 3c509 card
Date: Tue, 4 Apr 2006 10:52:38 +0200 [thread overview]
Message-ID: <20060404085238.GA24015@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <200603262143.k2QLhrDU002007@clem.clem-digital.net>
Hi,
On Sun, Mar 26, 2006 at 04:43:53PM -0500, Pete Clements wrote:
> FYI:
> Single 3c509 card, UP i386
> Lost networking with .16-git12, message
> ADDRCONF(NETDEV_UP): eth0: link is not ready
>
> Had several of these with git11
> NETDEV WATCHDOG: eth0: transmit timed out
>
> No problems observed git1-git10
Another "me too", in case it's still helpful.
3c905B (PCI) on a BNC(!) network, AMD Duron 1200, 3c59x.o.
2.6.15-ck7 (based on 2.6.15.6) works, 2.6.16-ck3 (based on 2.6.16.1)
produces the following errors:
Apr 3 19:10:41 birgit kernel: nfs: server gate not responding, still trying
Apr 3 19:10:52 birgit last message repeated 5 times
Apr 3 19:10:52 birgit kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 3 19:10:52 birgit kernel: eth0: transmit timed out, tx_status 00 status e000.
Apr 3 19:10:52 birgit kernel: diagnostics: net 04c0 media 4800 dma 000000a0 fif
o 0000
Apr 3 19:10:52 birgit kernel: Flags; bus-master 1, dirty 19952(0) current 19968
(0)
Apr 3 19:10:52 birgit kernel: Transmit list 1f53f2a0 vs. df53f200.
Apr 3 19:10:52 birgit kernel: 0: @df53f200 length 8000009e status 0c01009e
Apr 3 19:10:52 birgit kernel: 1: @df53f2a0 length 8000009e status 0c00009e
Apr 3 19:10:52 birgit kernel: 2: @df53f340 length 8000009e status 0c00009e
Apr 3 19:10:52 birgit kernel: 3: @df53f3e0 length 8000009e status 0c00009e
Apr 3 19:10:52 birgit kernel: 4: @df53f480 length 8000009e status 0c00009e
Apr 3 19:10:52 birgit kernel: 5: @df53f520 length 8000009e status 0c00009e
Apr 3 19:10:52 birgit kernel: 6: @df53f5c0 length 80000042 status 00000042
Apr 3 19:10:52 birgit kernel: 7: @df53f660 length 80000042 status 00000042
Apr 3 19:10:52 birgit kernel: 8: @df53f700 length 80000072 status 0c000072
Apr 3 19:10:52 birgit kernel: 9: @df53f7a0 length 8000009e status 0c00009e
Apr 3 19:10:52 birgit kernel: 10: @df53f840 length 8000004e status 0000004e
Apr 3 19:10:52 birgit kernel: 11: @df53f8e0 length 8000009e status 0c00009e
Apr 3 19:10:52 birgit kernel: 12: @df53f980 length 8000004e status 0000004e
Apr 3 19:10:52 birgit kernel: 13: @df53fa20 length 8000004e status 0000004e
Apr 3 19:10:52 birgit kernel: 14: @df53fac0 length 8000009e status 8c00009e
Apr 3 19:10:52 birgit kernel: 15: @df53fb60 length 80000072 status 8c000072
Apr 3 19:10:52 birgit kernel: eth0: Resetting the Tx ring pointer.
Apr 3 19:10:52 birgit kernel: nfs: server gate OK
Would be very nice (~= important) to see a fix somewhere in 2.6.16.y.
Andreas Mohr
prev parent reply other threads:[~2006-04-04 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 21:43 Pete Clements
2006-04-04 8:52 ` Andreas Mohr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060404085238.GA24015@rhlx01.fht-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=clem@clem.clem-digital.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®