Date: Tue, 13 Sep 2005 15:28:30 -0700
From: Chris Wright <chrisw@osdl.org>
To: Andy Stewart <andystewart@comcast.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.6.13 BUG tg3.c:2805 = crash (this one isn't tainted)
Message-ID: <20050913222830.GG7991@shell0.pdx.osdl.net>
References: <43263CDC.1010604@comcast.net> <43264C1C.9030207@comcast.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43264C1C.9030207@comcast.net>
User-Agent: Mutt/1.5.6i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1022
Lines: 24

* Andy Stewart (andystewart@comcast.net) wrote:
> I think I have an idea of what I can do to cause this to occur:
> 
> 1) Run setiathome(boinc) so both CPUs are at 100% (nice) utilization
> 2) Run rsync to sync a few GB between machines on a 100 Mb ethernet network
> 3) Notice puzzlingly slow interactive response time with high (8-10)
> load average.
> 4) Click the mouse a bunch of times here, there, everywhere in
> frustration with 3(above)
> 5) I caused the crash within about 5 minutes.  I may be able to
> reproduce it - not sure.

Might help to copy netdev on the report.  Seems you've had a bit of luck
in reproducing.  Any chance on narrowing down to last known good kernel?
There's been a fair bit of change in that driver between 2.6.12 and
2.6.13.

thanks,
-chris
-
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/