From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Gospodarek Subject: Re: [Bugme-new] [Bug 9990] New: tg3: eth0: The system may be re-ordering memory-mapped I/O cycles Date: Thu, 14 Feb 2008 17:12:34 -0500 Message-ID: <20080214221234.GL856@gospo.usersys.redhat.com> References: <20080214102425.0fc8e3c1.akpm@linux-foundation.org> <20080214185627.GK856@gospo.usersys.redhat.com> <1203024327.13495.21.camel@dell> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andy Gospodarek , Andrew Morton , Matt Carlson , bugme-daemon@bugzilla.kernel.org, netdev , ralf.hildebrandt@charite.de To: Michael Chan Return-path: Received: from mx1.redhat.com ([66.187.233.31]:59816 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754451AbYBNWMr (ORCPT ); Thu, 14 Feb 2008 17:12:47 -0500 Content-Disposition: inline In-Reply-To: <1203024327.13495.21.camel@dell> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Feb 14, 2008 at 01:25:27PM -0800, Michael Chan wrote: > On Thu, 2008-02-14 at 13:56 -0500, Andy Gospodarek wrote: > > On Thu, Feb 14, 2008 at 10:24:25AM -0800, Andrew Morton wrote: > > > On Thu, 14 Feb 2008 01:59:12 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote: > > > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=9990 > > > > > > > > Summary: tg3: eth0: The system may be re-ordering memory-mapped > > > > I/O cycles > > > > Product: Drivers > > > > Version: 2.5 > > > > KernelVersion: 2.6.24-git18 > > > > Platform: All > > > > OS/Version: Linux > > > > Tree: Mainline > > > > Status: NEW > > > > Severity: normal > > > > Priority: P1 > > > > Component: Network > > > > AssignedTo: jgarzik@pobox.com > > > > ReportedBy: ralf.hildebrandt@charite.de > > > > > > > > > > > > That should be a simple matter of adding the right pci-ids to > > tg3_get_invariants -- hopefully Ralf will respond and we can get that > > knocked out quickly. > > > > > > It doesn't look like it was re-ordered IO. If it was, it should have > self-recovered without hitting the BUG(). > Good catch, Michael! I missed that it paniced since I expect to see some sort of backtrace when that happens. We should try and get that bridge added to the list though, to avoid repeated complaints that there is a tg3 bug.