From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Theodore Tso <tytso@mit.edu>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, mchan@broadcom.com
Subject: Re: [PATCH -rt DO NOT APPLY] Fix for tg3 networking lockup
Date: Thu, 3 Aug 2006 18:04:55 +0100 [thread overview]
Message-ID: <200608031804.55292.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <20060803094917.8280f5ff.rdunlap@xenotime.net>
On Thursday 03 August 2006 17:49, Randy.Dunlap wrote:
[snip]
> > This only shows up with the real-time kernel where timer softirq's run
> > in their own processes, and a high priority process preempts the timer
> > softirq. I don't really consider this a networking bug, or even
> > driver bug, although it does seem unfortunate that Broadcom hardware
> > locks up and goes unresponsive if the OS doesn't tickle it every tenth
> > of a second or so. (Definitely a bad idea if the tg3 gets used on any
> > laptops, from a power usage perspective.) But that seems like a
> > (lame) hardware bug, not a driver bug....
>
> Interesting. On my Dell D610 notebook with tg3 and vpn,
> I have to ping a server on the vpn to keep it alive, otherwise
> it disappears soon and I have to restart the vpn. Of course,
> this could just be the vpn or some other software problem
> instead of a tg3 problem.
Probably. I have an NC6000 with a tg3 and have never experienced link failure
problems, even under -rt.
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-08-03 17:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:57 Theodore Tso
2006-08-03 10:00 ` Herbert Xu
2006-08-03 16:32 ` Theodore Tso
2006-08-03 16:46 ` Daniel Walker
2006-08-03 17:17 ` Theodore Tso
2006-08-03 21:45 ` David Miller
2006-08-03 16:49 ` Randy.Dunlap
2006-08-03 17:04 ` Alistair John Strachan [this message]
2006-08-03 21:43 ` David Miller
2006-08-03 17:28 ` Theodore Tso
2006-08-03 18:36 ` Michael Chan
2006-08-03 20:17 ` Theodore Tso
2006-08-03 21:48 ` David Miller
2006-08-03 23:28 ` Michael Chan
2006-08-03 23:43 ` David Miller
2006-08-04 0:07 ` Theodore Tso
2006-08-04 0:20 ` David Miller
2006-08-04 0:25 ` Arjan van de Ven
2006-08-04 3:23 ` Theodore Tso
2006-08-04 3:45 ` Michael Chan
2006-08-05 20:26 ` Theodore Tso
2006-08-08 6:36 ` Michael Chan
2006-08-03 23:53 ` Theodore Tso
2006-08-03 23:56 ` David Miller
2006-08-03 23:59 ` Herbert Xu
2006-08-04 0:01 ` David Miller
2006-08-04 0:16 ` Michael Chan
2006-08-04 0:03 ` Daniel Walker
2006-08-07 5:34 ` Steven Rostedt
2006-08-07 6:18 ` David Miller
2006-08-08 12:24 ` Steven Rostedt
2006-08-08 13:13 ` Steven Rostedt
2006-08-08 22:00 ` David Miller
2006-08-08 22:27 ` Steven Rostedt
2006-08-09 11:29 ` Roman Zippel
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=200608031804.55292.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®