From: Oliver Feiler <kiza@gmx.net>
To: Len Brown <len.brown@intel.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Marcelo Tosatti <marcelo@hera.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: eth*: transmit timed out since .27
Date: Mon, 16 Aug 2004 21:08:57 +0200 [thread overview]
Message-ID: <41210649.4090008@gmx.net> (raw)
In-Reply-To: <41210098.4080904@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
Oliver Feiler wrote:
>
>
> Ok, I've turned on the IOAPIC and it seems to work perfectly fine.
> Except for that IRQ 255 thing I've noticed no oddities. Thanks for the
> hint. :)
No, not quite. After about 30 minutes of uptime and a moderate load of
eth0 (100-200KB/s constant data flow) it happened again. :(
Aug 16 21:03:13 spot kernel: eth0: Tx timed out, lost interrupt?
TSR=0x3, ISR=0x97, t=36.
Aug 16 21:03:15 spot kernel: eth0: Tx timed out, lost interrupt?
TSR=0x3, ISR=0x3, t=141.
Aug 16 21:03:23 spot kernel: eth0: Tx timed out, lost interrupt?
TSR=0x3, ISR=0x3, t=545.
[repeating endlessly]
I've booted a kernel without APIC and IOAPIC compiled and it works again.
I'm attaching a dmesg from a boot with IOAPIC enabled. I don't really
know where to look for the problem here. The interrupt counter for the
IRQ eth0 is using (a Realtek 8029 chipset) is growing significantly
after a while. And after a while is seems to get stuck (Tx timed out).
"ifconfig eth0 down" and "up" again did nothing. Sometimes it seems to
fix such network problems.
cu
Oliver
[-- Attachment #2: dmesg-2.4.27-ioapic.gz --]
[-- Type: application/x-gzip, Size: 4878 bytes --]
next prev parent reply other threads:[~2004-08-16 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <566B962EB122634D86E6EE29E83DD808182C3236@hdsmsx403.hd.intel.com>
2004-08-16 17:52 ` eth*: transmit timed out since .27 (was: linux-2.4.27 released) Len Brown
2004-08-16 18:44 ` eth*: transmit timed out since .27 Oliver Feiler
2004-08-16 19:08 ` Oliver Feiler [this message]
2004-08-16 19:50 ` Len Brown
2004-08-16 23:04 ` Oliver Feiler
2004-08-16 23:42 ` Maciej W. Rozycki
2004-08-17 0:29 ` Alan Cox
2004-08-16 19:38 ` Len Brown
2004-08-16 20:11 ` Maciej W. Rozycki
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=41210649.4090008@gmx.net \
--to=kiza@gmx.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=marcelo@hera.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.