From: Andrew Morton <akpm@osdl.org>
To: Ralf Gerbig <rge@quengel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc2-mm1 (8139too interrupt)
Date: Wed, 17 Nov 2004 11:06:40 -0800 [thread overview]
Message-ID: <20041117110640.1c7ccccd.akpm@osdl.org> (raw)
In-Reply-To: <87lld0rb2i.fsf-news@hsp-law.de>
Ralf Gerbig <rge@quengel.org> 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.
Thanks.
next prev parent reply other threads:[~2004-11-17 19:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 9:42 2.6.10-rc2-mm1 Andrew Morton
2004-11-16 16:48 ` 2.6.10-rc2-mm1 - SELinux atomic_dec_and_test() bug James Morris
2004-11-16 21:30 ` 2.6.10-rc2-mm1 Lee Revell
2004-11-17 2:22 ` 2.6.10-rc2-mm1 Andrew Morton
2004-11-17 2:28 ` 2.6.10-rc2-mm1 Lee Revell
2004-11-17 3:21 ` 2.6.10-rc2-mm1 Dave Airlie
2004-11-17 3:23 ` 2.6.10-rc2-mm1 Lee Revell
2004-11-17 22:08 ` 2.6.10-rc2-mm1 Dave Airlie
2004-11-16 21:38 ` 2.6.10-rc2-mm1 Lee Revell
2004-11-17 11:04 ` 2.6.10-rc2-mm1 (8139too interrupt) Ralf Gerbig
2004-11-17 19:06 ` Andrew Morton [this message]
2004-11-17 22:18 ` Ralf Gerbig
2004-11-18 20:46 ` Ralf Gerbig
2004-11-19 7:48 ` Dave Airlie
2004-11-19 8:12 ` Dave Airlie
2004-11-23 7:55 ` Dave Airlie
2004-11-17 11:32 ` 2.6.10-rc2-mm1 William Lee Irwin III
2004-11-17 12:34 ` 2.6.10-rc2-mm1 William Lee Irwin III
2004-11-17 12:56 ` 2.6.10-rc2-mm1 William Lee Irwin III
2004-11-18 10:22 ` 2.6.10-rc2-mm1 William Lee Irwin III
2004-11-18 10:31 ` 2.6.10-rc2-mm1 Andrew Morton
2004-11-19 7:57 ` 2.6.10-rc2-mm1 William Lee Irwin III
2004-11-17 20:53 ` 2.6.10-rc2-mm1 Grzegorz Piotr Jaskiewicz
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=20041117110640.1c7ccccd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rge@quengel.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