From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: "David S. Miller" <davem@redhat.com>,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.2 crash after network link failure
Date: Tue, 10 Feb 2004 15:11:19 +0100 [thread overview]
Message-ID: <20040210141118.GA14719@vana.vc.cvut.cz> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E0102CBDE6C@orsmsx402.jf.intel.com>
On Mon, Feb 09, 2004 at 03:37:48PM -0800, Feldman, Scott wrote:
> > I think what might be happening is that somehow the TX queue
> > is corrupted if
> > e100_config() runs (due to link UP state change) while there
> > are active normal SKB packets on the TX queue. Or perhaps
> > some TX queue handling locking issue.
> >
> > Scott, any ideas?
>
> e100 hardware will continue to process the hardware's Tx queue even
> after link is lost, and then cleanup (return skbs) on interrupt. I
> would expect e100 to be holding no Tx skbs when link returned.
>
> Petr, -mm kernel has an updated (and much simpler) e100 driver. Is this
> something you can try? The switch failure can be simulated by manually
> plugging the cable in/out.
Unfortunately it does not seem easily triggerable. I spent about one
hour plugging/unplugging cable while transmitting UDP packets as fast
as possible, sometime interleaved with 'mii-tool -r', and it refused
to crash...
Petr Vandrovec
next prev parent reply other threads:[~2004-02-10 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 23:37 Feldman, Scott
2004-02-10 14:11 ` Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-09 13:01 Petr Vandrovec
2004-02-09 22:28 ` David S. Miller
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=20040210141118.GA14719@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.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
all inboxes | Powered by JetHome®