[lkml]   [2004]   [Nov]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.10-rc2-mm1 (8139too interrupt)
Ralf Gerbig <> wrote:
> ...
> [ide_intr+0/496] (ide_intr+0x0/0x1f0)
> [<c0269c80>] (ide_intr+0x0/0x1f0)
> [ide_intr+0/496] (ide_intr+0x0/0x1f0)
> [<c0269c80>] (ide_intr+0x0/0x1f0)
> [pg0+541642080/1068946432] (rtl8139_interrupt+0x0/0x1d0 [8139too])
> [<e091dd60>] (rtl8139_interrupt+0x0/0x1d0 [8139too])
> Disabling IRQ #19
> NETDEV WATCHDOG: eth1: transmit timed out
> eth1: Transmit timeout, status 0c 0005 c07f media 18.
> eth1: Tx queue start entry 63 dirty entry 59.
> eth1: Tx descriptor 0 is 0008a03c.
> eth1: Tx descriptor 1 is 0008a06a.
> eth1: Tx descriptor 2 is 0008a03c.
> eth1: Tx descriptor 3 is 0008a03c. (queue head)
> eth1: link up, 10Mbps, full-duplex, lpa 0x4061
> and the interface is dead. Rmmod/insmod does not help.

Does this happen immediately, or does it take a bit of load first?

We should be looking for changes in 8139too, changes in IDE or changes in
interrupt setup. Usually it is the latter. It would be helpful if you
could gather the boot-time dmesg output from rc1-mm5 and rc2-mm1 and do a
`diff -u', see what changed.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:08    [W:0.097 / U:0.232 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site