Date: Thu, 03 Aug 2006 16:56:54 -0700 (PDT)
Message-Id: <20060803.165654.45876296.davem@davemloft.net>
To: tytso@mit.edu
Cc: mchan@broadcom.com, herbert@gondor.apana.org.au,
       linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH -rt DO NOT APPLY] Fix for tg3 networking lockup
From: David Miller <davem@davemloft.net>
In-Reply-To: <20060803235326.GC7894@thunk.org>
References: <20060803201741.GA7894@thunk.org>
	<20060803.144845.66061203.davem@davemloft.net>
	<20060803235326.GC7894@thunk.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 691
Lines: 16

From: Theodore Tso <tytso@mit.edu>
Date: Thu, 3 Aug 2006 19:53:26 -0400

> Any suggestions on how I could figure out what was really going on and
> what would be a better fix would be greatly appreciated.

As Michael explained, it's the ASF heartbeat sent by tg3_timer() that
must be delivered to the chip within certain timing constraints.

If you had any watchdog devices on this machine, they would likely
trigger too and reset your machine :)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/