public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andreas Schwarz <usenet.2117@andreas-s.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 8139too & APIC incompatibility (2.6.0-test6-mm1, 2.4.20)
Date: Mon, 29 Sep 2003 12:55:50 -0400	[thread overview]
Message-ID: <20030929165550.GA6526@gtf.org> (raw)
In-Reply-To: <slrnbngl0o.4e0.usenet.2117@home.andreas-s.net>

On Mon, Sep 29, 2003 at 03:47:29PM +0000, Andreas Schwarz wrote:
> When APIC is activated, the following messages appear in syslog from
> time to time:                                                                   
>                                                                                 
> kernel: NETDEV WATCHDOG: eth1: transmit timed out
> kernel: eth1: Tx queue start entry 4  dirty entry 0.
> kernel: eth1:  Tx descriptor 0 is 00002000. (queue head)
> kernel: eth1:  Tx descriptor 1 is 00002000.
> kernel: eth1:  Tx descriptor 2 is 00002000.
> kernel: eth1:  Tx descriptor 3 is 00002000.
> kernel: eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
> 
> After this has happened the first time, the card fails to send or
> receive any more packages.

Yes.  Has nothing to do with 8139too, though.

This is one of 1001 similar symptoms of the same problem, "interrupt
routing bug(s)".

	Jeff




  reply	other threads:[~2003-09-29 16:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 15:47 8139too & APIC incompatibility (2.6.0-test6-mm1, 2.4.20) Andreas Schwarz
2003-09-29 16:55 ` Jeff Garzik [this message]
2003-10-11 18:23   ` Interrupt routing (was Re: 8139too & APIC incompatibility (2.6.0-test6-mm1, 2.4.20)) Jonathan McDowell

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=20030929165550.GA6526@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=usenet.2117@andreas-s.net \
    /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