netdev
[Top] [All Lists]

RE: 2.6.2 crash after network link failure

To: "David S. Miller" <davem@xxxxxxxxxx>, "Petr Vandrovec" <vandrove@xxxxxxxxxx>
Subject: RE: 2.6.2 crash after network link failure
From: "Feldman, Scott" <scott.feldman@xxxxxxxxx>
Date: Mon, 9 Feb 2004 15:37:48 -0800
Cc: <netdev@xxxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
Thread-index: AcPvXB5YoU0FjfWiRdS9E8hm8U19JwABoHEA
Thread-topic: 2.6.2 crash after network link failure
> 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.

-scott


<Prev in Thread] Current Thread [Next in Thread>