From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: Steffen Klassert <klassert@mathematik.tu-chemnitz.de>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NETDEV WATCHDOG (3Com 3c905 adapter)
Date: Sat, 24 Nov 2007 14:11:15 +0100 [thread overview]
Message-ID: <474822F3.6070803@systella.fr> (raw)
In-Reply-To: <20071124111425.GA29778@newton.mathematik.tu-chemnitz.de>
Steffen Klassert wrote:
> On Fri, Nov 23, 2007 at 04:52:39PM +0100, BERTRAND Joël wrote:
>> BERTRAND Joël wrote:
>>> Hello,
>>>
>>> Since I have installed a 2.6.23.1 linux kernel on my U60, I can see
>>> several NETDEV WATCHDOG. This trouble never occurs with 2.6.23-rc4.
>>> This bug occurs after a random uptime.
>> I have made the same constation this evening on a amd64/up with two
>> 3C905 and a 2.6.21.3 linux kernel... This evening, I have rebooted my
>> U60 with a 2.6.23.8 kernel and the same 3C905 runs fine. Wait and see
>> (but I suspect a kernel bug...).
>>
>> For main linux kernel list:
>>
>>> End of dmesg :
>>>
>>> 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?
>
> This looks like a problem that several network drivers had recently.
> The problem was genirq related and should be fixed in 2.6.23,
> so I'm surprised that this happens with 2.6.23.1 but not with 2.6.23-rc4.
I can confirm that my U60 worked fine sixty days with 2.6.23-rc4
without any trouble. With 2.6.23.1, 3com NIC hangs after three or four
days...
Regards,
JKB
prev parent reply other threads:[~2007-11-24 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4746C44B.8040008@systella.fr>
2007-11-23 15:52 ` NETDEV WATCHDOG (3Com 3c905 adapter) BERTRAND Joël
2007-11-24 11:14 ` Steffen Klassert
2007-11-24 13:11 ` BERTRAND Joël [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=474822F3.6070803@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=klassert@mathematik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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