netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: 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 12:32:05 -0400	[thread overview]
Message-ID: <20060803163204.GB20603@thunk.org> (raw)
In-Reply-To: <E1G8a0J-0002Pn-00@gondolin.me.apana.org.au>

On Thu, Aug 03, 2006 at 08:00:35PM +1000, Herbert Xu wrote:
> Theodore Tso <tytso@mit.edu> wrote:
> > 
> > I'm sending this on mostly because it was a bit of a pain to track down,
> > and hopefully it will save time if anyone else hits this while playing
> > with the -rt kernel.  It is NOT the right way to fix things, so please
> > don't even think of applying this patch (unless you need it, in your own
> > local tree :-).
> > 
> > One of these days when we have time to breath we'll look into fixing
> > this the right way, if someone doesn't beat us to it first.  :-)
> 
> You probably should resend the patch to netdev and Michael Chan
> <mchan@broadcom.com>.  He might have ideas on how this could be
> avoided.

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....

						- Ted


  reply	other threads:[~2006-08-03 16:32 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060803075704.GC27835@thunk.org>
2006-08-03 10:00 ` [PATCH -rt DO NOT APPLY] Fix for tg3 networking lockup Herbert Xu
2006-08-03 16:32   ` Theodore Tso [this message]
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
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-25 22:33                   ` Marc Bevand
2006-08-25 22:55                     ` Michael Chan
2006-08-25 23:48                       ` Marc Bevand
2006-08-26  0:01                         ` 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=20060803163204.GB20603@thunk.org \
    --to=tytso@mit.edu \
    --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 \
    /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).