From: Steffen Klassert <klassert@mathematik.tu-chemnitz.de>
To: mt@systella.fr, linux-kernel@vger.kernel.org
Subject: Re: NETDEV WATCHDOG on U60/SMP
Date: Fri, 20 Jun 2008 10:52:36 +0200 [thread overview]
Message-ID: <20080620085236.GA2376@bayes.mathematik.tu-chemnitz.de> (raw)
In-Reply-To: <485B6218.4090705@systella.fr>
On Fri, Jun 20, 2008 at 09:54:00AM +0200, BERTRAND Jo?l wrote:
> Hello,
>
> This mail comes from sparclinux mailing list. I repost it on general
> linux kernel mailing list because I'm not sure that this bug is sparc
> specific. Nevertheless, I can only reproduce it on sparc64/SMP.
>
> My U60 runs linux debian with official 2.6.25 linux kernel (I'm
> currently trying 2.6.25.7) and sometimes, when eth2 is stressed, eth2
> hangs with NETDEV WATCHDOG :
>
> NETDEV WATCHDOG: eth2: transmit timed out
> eth2: transmit timed out, tx_status 00 status 8601.
> diagnostics: net 0ccc media 8880 dma 0000003a fifo 0000
> eth2: Interrupt posted but not delivered -- IRQ blocked by another device?
> Flags; bus-master 1, dirty 2283344(0) current 2283344(0)
> Transmit list 00000000 vs. fffff800af098200.
> 0: @fffff800af098200 length 00000042 status 0c01059a
> 1: @fffff800af098260 length 00000042 status 0c01059a
> 2: @fffff800af0982c0 length 00000042 status 0c01059a
> 3: @fffff800af098320 length 00000042 status 0c01059a
> 4: @fffff800af098380 length 00000042 status 0c01059a
> 5: @fffff800af0983e0 length 00000042 status 0c01059a
> 6: @fffff800af098440 length 00000042 status 0c01059a
> 7: @fffff800af0984a0 length 00000042 status 0c01059a
> 8: @fffff800af098500 length 8000002a status 0001002a
> 9: @fffff800af098560 length 8000002a status 0001002a
> 10: @fffff800af0985c0 length 8000002a status 0001002a
> 11: @fffff800af098620 length 8000002a status 0001002a
> 12: @fffff800af098680 length 8000002a status 0001002a
> 13: @fffff800af0986e0 length 8000002a status 0001002a
> 14: @fffff800af098740 length 8000002a status 8001002a
> 15: @fffff800af0987a0 length 8000002a status 8001002a
> eth2: Resetting the Tx ring pointer.
> eth2: setting full-duplex.
Some people with similar problems reported, that they can workarround
their problems by increasing the rx/tx ring sizes of the 3c59x driver.
See http://bugzilla.kernel.org/show_bug.cgi?id=6444 for details.
Would be good to know whether this helps for your problem too.
Steffen
next prev parent reply other threads:[~2008-06-20 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 7:54 BERTRAND Joël
2008-06-20 8:52 ` Steffen Klassert [this message]
2008-06-20 10:19 ` BERTRAND Joel
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=20080620085236.GA2376@bayes.mathematik.tu-chemnitz.de \
--to=klassert@mathematik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mt@systella.fr \
/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®