netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 09:23:04 +0200	[thread overview]
Message-ID: <44B0AED8.3040604@better.se> (raw)
In-Reply-To: <44AFDA3B.6020904@tungstengraphics.com>

Thomas Hellström wrote:
> I guess you got the wrong commit, and the correct one should be the one
> where Dave adds vblank interrupts. It should be close to the one you
> listed.

I thought I double-checked that it was the right commit, but will check
again.

> If the network sits on the same IRQ line, it will be disabled as well.

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.)

> If you check your kernel logs, you will probably have
> messages about disabled IRQs.

Correct. Here's an example:

Jul  7 16:43:39 kelev kernel: irq 11: nobody cared (try booting with the
"irqpoll" option)
Jul  7 16:43:39 kelev kernel:  [<c0138b74>] __report_bad_irq+0x24/0x90
Jul  7 16:43:39 kelev kernel:  [<c0138c82>] note_interrupt+0x72/0xc0
Jul  7 16:43:39 kelev kernel:  [<c013862e>] __do_IRQ+0xae/0xc0
Jul  7 16:43:39 kelev kernel:  [<c0104a69>] do_IRQ+0x19/0x30
Jul  7 16:43:39 kelev kernel:  [<c01030c2>] common_interrupt+0x1a/0x20
Jul  7 16:43:39 kelev kernel:  [<c011c4fe>] __do_softirq+0x2e/0xa0
Jul  7 16:43:39 kelev kernel:  [<c011c597>] do_softirq+0x27/0x30
Jul  7 16:43:39 kelev kernel:  [<c0104a6e>] do_IRQ+0x1e/0x30
Jul  7 16:43:39 kelev kernel:  [<c01030c2>] common_interrupt+0x1a/0x20
Jul  7 16:43:39 kelev kernel:  [<c0102ef5>] syscall_call+0x7/0xb
Jul  7 16:43:39 kelev kernel: handlers:
Jul  7 16:43:39 kelev kernel: [<e01270c0>] (usb_hcd_irq+0x0/0x60 [usbcore])
Jul  7 16:43:39 kelev kernel: [<e01270c0>] (usb_hcd_irq+0x0/0x60 [usbcore])
Jul  7 16:43:39 kelev kernel: [<e0044160>] (rtl8139_interrupt+0x0/0x1d0
[8139too]
)
Jul  7 16:43:39 kelev kernel: Disabling IRQ #11

Jul  7 16:44:03 kelev kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul  7 16:44:03 kelev kernel: eth0: Transmit timeout, status 0c 0005
c07f media 9
0.
Jul  7 16:44:03 kelev kernel: eth0: Tx queue start entry 48  dirty entry 44.
Jul  7 16:44:03 kelev kernel: eth0:  Tx descriptor 0 is 0008a062. (queue
head)
Jul  7 16:44:03 kelev kernel: eth0:  Tx descriptor 1 is 0008a062.
Jul  7 16:44:03 kelev kernel: eth0:  Tx descriptor 2 is 0008a062.
Jul  7 16:44:03 kelev kernel: eth0:  Tx descriptor 3 is 0008a062.
Jul  7 16:44:03 kelev kernel: eth0: link up, 100Mbps, full-duplex, lpa
0x45E1



  reply	other threads:[~2006-07-09  7:23 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 [this message]
2006-07-09  7:34         ` Thomas Hellström
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=44B0AED8.3040604@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 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).