From: "Thomas Hellström" <thomas@tungstengraphics.com>
To: Marcus Better <marcus@better.se>
Cc: Dave Airlie <airlied@linux.ie>,
netdev@vger.kernel.org, dri-devel@lists.sourceforge.net,
Alan Hourihane <alanh@tungstengraphics.com>,
Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: rtl8139: NETDEV WATCHDOG: eth0: transmit timed out
Date: Sun, 09 Jul 2006 09:34:21 +0200 [thread overview]
Message-ID: <44B0B17D.10803@tungstengraphics.com> (raw)
In-Reply-To: <44B0AED8.3040604@better.se>
Marcus Better wrote:
>It appears to be on a different IRQ:
>~$ cat /proc/interrupts
> CPU0
> 0: 202574 XT-PIC timer
> 1: 2649 XT-PIC i8042
> 2: 0 XT-PIC cascade
> 8: 0 XT-PIC rtc
> 9: 0 XT-PIC acpi
> 10: 1059 XT-PIC yenta, Intel 82801CA-ICH3 Modem, Intel
>82801CA-ICH3
> 11: 40776 XT-PIC uhci_hcd:usb1, uhci_hcd:usb2, eth0
> 12: 100433 XT-PIC i8042
> 14: 63563 XT-PIC ide0
> 15: 6773 XT-PIC ide1
>NMI: 0
>ERR: 0
>
>(This is without i915 loaded though.)
>
>
>
Strange. I've also seen the i915 sending false interrupts on its own
line, though.
Does the "noirqdebug" option fix the problem?
/Thomas
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--
next prev parent reply other threads:[~2006-07-09 7:34 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 [this message]
2006-07-09 16:34 ` Marcus Better
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=44B0B17D.10803@tungstengraphics.com \
--to=thomas@tungstengraphics.com \
--cc=airlied@linux.ie \
--cc=alanh@tungstengraphics.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=marcus@better.se \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).