[Top] [All Lists]

Re: Mystery packet killing tg3

To: Stephen Hemminger <shemminger@xxxxxxxx>
Subject: Re: Mystery packet killing tg3
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
Date: Tue, 3 May 2005 15:39:54 -0700
Cc: mchan@xxxxxxxxxxxx, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20050503154500.0a53160d@xxxxxxxxxxxxxxxxx>
References: <20050502162405.65dfb4a9@xxxxxxxxxxxxxxxxxxxxx> <20050502200251.38271b61.davem@xxxxxxxxxxxxx> <20050503140528.1bd2ac74@xxxxxxxxxxxxxxxxx> <20050503141314.441c9d75.davem@xxxxxxxxxxxxx> <1115152907.15156.26.camel@rh4> <20050503150333.1ac1c159.davem@xxxxxxxxxxxxx> <20050503154500.0a53160d@xxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Tue, 3 May 2005 15:45:00 -0700
Stephen Hemminger <shemminger@xxxxxxxx> wrote:

> No, I forced it to always be true and still dies (when taking network down).

You're reproducing this pretty fast.

Does the link jam up, or are you just simply downing the interface
and the stop block messages are printed out?

If it jams up, what kind of traffic are you using to trigger this

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