From: Philip Molter <philip@datafoundry.com>
To: Michael Chan <mchan@broadcom.com>
Cc: netdev@vger.kernel.org
Subject: Re: tg3: tg3_stop_block timed out
Date: Tue, 12 Sep 2006 12:22:33 -0500 [thread overview]
Message-ID: <4506ECD9.4050607@datafoundry.com> (raw)
In-Reply-To: <1551EAE59135BE47B544934E30FC4FC093FAF4@NT-IRVA-0751.brcm.ad.broadcom.com>
> Please try the latest driver. If you still get the timeouts, I'll
> need to send you some debug patches to dump the state when these
> timeouts occur.
So far, with the new driver, I haven't seen any of these timeouts.
Normally, we'd have seen them by now. If they recur at some point in
the future, I'll post a new message.
Thanks for your help, Michael.
Philip
next prev parent reply other threads:[~2006-09-12 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 22:43 tg3: tg3_stop_block timed out Bernd Schubert
2006-08-07 23:07 ` Michael Chan
2006-08-07 23:24 ` Bernd Schubert
2006-08-07 23:46 ` Michael Chan
2006-08-09 14:44 ` Philip Molter
2006-09-03 22:35 ` Philip Molter
2006-09-04 18:25 ` Michael Chan
2006-09-04 21:27 ` Philip Molter
2006-09-12 17:22 ` Philip Molter [this message]
2006-08-09 15:20 ` Bernd Schubert
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=4506ECD9.4050607@datafoundry.com \
--to=philip@datafoundry.com \
--cc=mchan@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).