From: Oliver Feiler <kiza@gmx.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Marcelo Tosatti <marcelo@hera.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: eth*: transmit timed out since .27 (was: linux-2.4.27 released)
Date: Fri, 13 Aug 2004 23:56:25 +0200 [thread overview]
Message-ID: <200408132356.31778.kiza@gmx.net> (raw)
In-Reply-To: <20040813101525.GD24479@logos.cnet>
[-- Attachment #1.1: body text --]
[-- Type: text/plain, Size: 4036 bytes --]
Hi Marcelo,
On Friday 13 August 2004 12:15, Marcelo Tosatti wrote:
> On Tue, Aug 10, 2004 at 02:23:34PM +0200, Oliver Feiler wrote:
> > Hi,
> >
> > I've upgraded a server from .26 to .27, but ran into problems with the
> > network cards.
> >
> > The kernel throws a lot of errors into the syslog and the net devices
> > don't work:
> > Aug 10 13:39:25 spot kernel: NETDEV WATCHDOG: eth0: transmit timed out
> > Aug 10 13:39:26 spot kernel: NETDEV WATCHDOG: eth1: transmit timed out
> > Aug 10 13:39:26 spot kernel: eth1: Transmit timeout, status 00000004
> > 00000249 Aug 10 13:39:34 spot kernel: NETDEV WATCHDOG: eth1: transmit
> > timed out Aug 10 13:39:34 spot kernel: eth1: Transmit timeout, status
> > 00000004 00000241 Aug 10 13:39:42 spot kernel: NETDEV WATCHDOG: eth1:
> > transmit timed out Aug 10 13:39:42 spot kernel: eth1: Transmit timeout,
> > status 00000004 00000240 [...]
> >
> > and:
> > Aug 10 13:39:25 spot kernel: eth0: Tx timed out, lost interrupt? TSR=0x3,
> > ISR=0x3, t=515.
> > Aug 10 13:40:25 spot kernel: eth0: Tx timed out, lost interrupt? TSR=0x3,
> > ISR=0x3, t=5015.
> > Aug 10 13:40:40 spot kernel: eth0: Tx timed out, lost interrupt? TSR=0x3,
> > ISR=0x3, t=1014.
> > [...]
> >
> > The system has three network cards.
> > eth0: SIS900 (sis900.c)
> > eth1: RTL-8029 (ne2k-pci.c)
> > eth2: onboard VIA VT6102 Rhine-II (via-rhine.c)
> >
> > eth0 and eth1 share the same interrupt
> >
> > CPU0
> > 0: 91986 XT-PIC timer
> > 1: 935 XT-PIC keyboard
> > 2: 0 XT-PIC cascade
> > 8: 1 XT-PIC rtc
> > 9: 0 XT-PIC acpi
> > 10: 25109 XT-PIC via82cxxx, usb-uhci, usb-uhci, eth0,
> > eth1 11: 24 XT-PIC usb-uhci, eth2
> > 14: 7523 XT-PIC ide0
> > 15: 7021 XT-PIC ide1
> > NMI: 0
> > ERR: 0
>
> Wow, you have four devices on the same interrupt line. /proc/interrupts
> from 2.4.26/27 looks the same?
There are five on int10. ;) It's worse on my desktop box with six devices on
int11. But hey, Linux works just fine so I never cared.
Yes, /proc/interrupts from .26 and .27 is the same.
> > Either way .27 doesn't want to boot. I've attached dmesg from a running
> > 2.4.26 kernel and the config used for 2.4.27.
>
> You mean it boots but you get the Tx timeouts?
Yes.
> Well there are some changes to sis900 between .26 and .27 but I doubt
> they could be causing it.
>
> Can you try to boot with ACPI disabled? I think the problem might be
> related to ACPI configuration.
>
> Also, can you post the boot messages from 2.4.27?
I've attached three boots with .27. One without any parameters, one with
acpi=off and pci=noacpi (the way I booted previous kernels).
It seems I've found the problem. The network errors were caused by the
pci=noacpi boot parameter. Once I boot without any parameter or acpi=off it
works just fine.
Btw, how can I boot with ACPI disabled? I thought it was acpi=off, but it
doesn't seem to make any difference, the kernel still uses ACPI (see
dmesg-2.4.27-acpi=off.gz attachement).
Also there must have been some (positive) changes to ACPI in 2.4.27? With
earlier kernels I had this problem:
Feb 6 18:31:27 spot kernel: PCI: Using ACPI for IRQ routing
Feb 6 18:31:27 spot kernel: PCI: if you experience problems, try using option
'pci=noacpi' or even 'acpi=off'
[...]
Feb 6 18:31:27 spot kernel: PCI: No IRQ known for interrupt pin A of device
00:11.1 - using IRQ 255
This seems to have been corrected as of 2.4.27. I still get the
PCI: No IRQ known for interrupt pin A of device 00:11.1
warning, but it doesn't assign IRQ 255 anymore which I take as a good sign. :)
So, it seems to work fine now. If you still want me to test something
regarding ACPI on this mainboard feel free to ask.
Thanks for your help,
Oliver
--
Oliver Feiler - http://kiza.kcore.de/
[-- Attachment #1.2: dmesg-2.4.27-acpi.gz --]
[-- Type: application/x-gzip, Size: 3854 bytes --]
[-- Attachment #1.3: dmesg-2.4.27-acpi=off.gz --]
[-- Type: application/x-gzip, Size: 3867 bytes --]
[-- Attachment #1.4: dmesg-2.4.27-pci=noacpi.gz --]
[-- Type: application/x-gzip, Size: 3945 bytes --]
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-13 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 23:28 linux-2.4.27 released Marcelo Tosatti
2004-08-10 12:23 ` eth*: transmit timed out since .27 (was: linux-2.4.27 released) Oliver Feiler
2004-08-13 10:15 ` Marcelo Tosatti
2004-08-13 21:56 ` Oliver Feiler [this message]
2004-08-12 18:17 ` linux-2.4.27 released William Lee Irwin III
2004-08-12 18:18 ` William Lee Irwin III
[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
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=200408132356.31778.kiza@gmx.net \
--to=kiza@gmx.net \
--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.