All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Michael Chan <mchan@broadcom.com>
Cc: netdev@oss.sgi.com
Subject: Re: tg3 access hangs on system shutdown with 2.6.11-rc5, tg3_stop_block timed out
Date: Mon, 28 Feb 2005 22:39:05 +0100	[thread overview]
Message-ID: <20050228213905.GA20109@suse.de> (raw)
In-Reply-To: <B1508D50A0692F42B217C22C02D84972020F3DD2@NT-IRVA-0741.brcm.ad.broadcom.com>

 On Mon, Feb 28, Michael Chan wrote:

> The 5704S changes in 2.6.11-rc4 are mainly related to serdes link-up and tx
> signal. I don't see how those changes can cause a hang or the tg3_stop_block
> error. The stack trace did not show any tg3 function calls. Can you narrow it
> down further to a specific patch that is causing the problem?

The blades are currently busy with other testing for the rest of the
week. I ran 2.6.11-rc kernels since a while and it did not happen until
very recently.

  reply	other threads:[~2005-02-28 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-28 21:33 tg3 access hangs on system shutdown with 2.6.11-rc5, tg3_stop_block timed out Michael Chan
2005-02-28 21:39 ` Olaf Hering [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-26 16:18 Olaf Hering

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=20050228213905.GA20109@suse.de \
    --to=olh@suse.de \
    --cc=mchan@broadcom.com \
    --cc=netdev@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.