On Thu, 2006-02-02 at 13:37 +, Mike Crowe wrote:
>> I'm running the Debian 2.6.15 kernel from backports.org on a
>> machine with two Opteron 275s. I am getting a BUG in tg3.c quite
>> reliably if I ping flood the machine from a few others and cause a
>> bit of other network activity. Sometimes
On Thu, 2006-02-02 at 22:05 +, Mike Crowe wrote:
>> Perhaps this new problem is unrelated. I shall try and reproduce
>> it. Is there anything I should try when the interface is locked up to
>> help?
On Thu, Feb 02, 2006 at 12:49:53PM -0800, Michael Chan wrote:
> Did this setup use to work bef
On Thu, 2006-02-02 at 22:05 +, Mike Crowe wrote:
> Perhaps this new problem is unrelated. I shall try and reproduce
> it. Is there anything I should try when the interface is locked up to
> help?
>
1. Run ethtool -d eth? > before you get a NETDEV WATCHDOG
timeout and before you do ifdown. P
On Thu, 2006-02-02 at 13:37 +, I wrote:
>> I'm running the Debian 2.6.15 kernel from backports.org on a machine
>> with two Opteron 275s. I am getting a BUG in tg3.c quite reliably if I
>> ping flood the machine from a few others and cause a bit of other
>> network activity. Sometimes it takes
On Thu, 2006-02-02 at 13:37 +, Mike Crowe wrote:
> I'm running the Debian 2.6.15 kernel from backports.org on a machine
> with two Opteron 275s. I am getting a BUG in tg3.c quite reliably if I
> ping flood the machine from a few others and cause a bit of other
> network activity. Sometimes it t
I'm running the Debian 2.6.15 kernel from backports.org on a machine
with two Opteron 275s. I am getting a BUG in tg3.c quite reliably if I
ping flood the machine from a few others and cause a bit of other
network activity. Sometimes it takes a few minutes, sometimes half an
hour. The BUG also fire
