From: Marcus Better <marcus@better.se>
To: "Thomas Hellström" <thomas@tungstengraphics.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
Dave Airlie <airlied@linux.ie>,
netdev@vger.kernel.org, dri-devel@lists.sourceforge.net,
Alan Hourihane <alanh@tungstengraphics.com>
Subject: Re: rtl8139: NETDEV WATCHDOG: eth0: transmit timed out
Date: Sun, 09 Jul 2006 18:34:51 +0200 [thread overview]
Message-ID: <44B1302B.5060207@better.se> (raw)
In-Reply-To: <44B0B17D.10803@tungstengraphics.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thomas Hellström wrote:
> Strange. I've also seen the i915 sending false interrupts on its own
> line, though.
Here's the interrupt table with i915 loaded:
~$ cat /proc/interrupts
CPU0
0: 401031 XT-PIC timer
1: 3681 XT-PIC i8042
2: 0 XT-PIC cascade
8: 0 XT-PIC rtc
9: 0 XT-PIC acpi
10: 997 XT-PIC yenta, Intel 82801CA-ICH3, Intel
82801CA-ICH3 Modem
11: 93823 XT-PIC uhci_hcd:usb1, uhci_hcd:usb2, eth0,
i915@pci:0000:00:02.0
12: 75631 XT-PIC i8042
14: 18284 XT-PIC ide0
15: 13901 XT-PIC ide1
NMI: 0
ERR: 0
> Does the "noirqdebug" option fix the problem?
Yes, it appears to fix it.
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEsTArXjXn6TzcAQkRAn/vAKCZUAVd45xQae4FthvNr68x/jTS4QCgyE7N
CzPv0R9okmIjrsGykMXrfPk=
=gU6D
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-07-09 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 9:23 rtl8139: NETDEV WATCHDOG: eth0: transmit timed out Marcus Better
2006-06-30 21:16 ` Francois Romieu
2006-07-04 19:38 ` Marcus Better
2006-07-07 16:32 ` Marcus Better
2006-07-08 16:15 ` Thomas Hellström
2006-07-09 7:23 ` Marcus Better
2006-07-09 7:34 ` Thomas Hellström
2006-07-09 16:34 ` Marcus Better [this message]
2006-07-10 13:02 ` Marcus Better
2006-07-10 13:10 ` Thomas Hellström
2006-07-10 13:17 ` Marcus Better
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=44B1302B.5060207@better.se \
--to=marcus@better.se \
--cc=airlied@linux.ie \
--cc=alanh@tungstengraphics.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=thomas@tungstengraphics.com \
/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.