netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "Bernhard Schmidt" <berni@birkenwald.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Matthew Carlson" <mcarlson@broadcom.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"bugme-daemon@bugzilla.kernel.org"
	<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 12877] New: tg3: eth0 transit timed out, resetting -> dead NIC
Date: Tue, 17 Mar 2009 16:30:34 -0700	[thread overview]
Message-ID: <1237332634.12207.11.camel@HP1> (raw)
In-Reply-To: <49C01F7F.9030306@birkenwald.de>


On Tue, 2009-03-17 at 15:09 -0700, Bernhard Schmidt wrote:
> Attached, both after the crash (tg3.crashed) and after I reloaded the 
> module (tg3.reloaded). Additional info, ifdown/ifup does not fix the 
> situation, both take pretty long
> 

Thanks for the information.  The memory enable bit in the PCI command
register was cleared during tx_timeout.  That's why all the registers
were reading 0xffffffff.  The tx_timeout code in tg3 would not be able
to reset the chip if that bit was cleared.  We need to find out why that
bit was cleared.  We should also enhance the tx timeout code so that it
can recover more completely even if the memory enable bit is cleared.

Thanks.



  reply	other threads:[~2009-03-17 23:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12877-10286@http.bugzilla.kernel.org/>
2009-03-15 21:32 ` [Bugme-new] [Bug 12877] New: tg3: eth0 transit timed out, resetting -> dead NIC Andrew Morton
2009-03-16 21:23   ` Michael Chan
2009-03-16 22:46     ` Bernhard Schmidt
2009-03-17 22:09     ` Bernhard Schmidt
2009-03-17 23:30       ` Michael Chan [this message]
2009-03-19 16:58       ` Matt Carlson
2009-03-19 18:06         ` Bernhard Schmidt
2009-03-19 18:15           ` Matt Carlson
2009-03-19 18:19             ` Bernhard Schmidt
2009-03-22 13:21         ` Bernhard Schmidt
2009-03-23 18:18           ` Matt Carlson
2009-03-24  0:35             ` Bernhard Schmidt
2009-03-31 16:26           ` Matt Carlson
2009-03-31 22:16             ` Bernhard Schmidt
2009-04-13 21:54               ` Bernhard Schmidt
2009-04-14 18:29                 ` Matt Carlson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1237332634.12207.11.camel@HP1 \
    --to=mchan@broadcom.com \
    --cc=akpm@linux-foundation.org \
    --cc=berni@birkenwald.de \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=mcarlson@broadcom.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).