netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: netdev@vger.kernel.org
Subject: Re: Debugging kernel lockups during network activity
Date: Fri, 28 Jul 2006 16:39:10 +0200	[thread overview]
Message-ID: <44CA218E.6040502@o2.pl> (raw)
In-Reply-To: <20060727181943.GD23091@artsapartment.org>

On 27-07-2006 20:19, Art Haas wrote:
> Hi.
> 
> I've got Fedora Rawhide running on a SMP PIII machine, and the latest
> kernels from Fedora have been locking up when I run 'yum update' to
> get the latest packages. I also experience lock-ups when I use
> Firefox to do some web browsing. Not all my network usage results in a
> lockup, however. I can usually do 'git pull' and update git itself or
> my copy of Linus' kernel tree without problems, as well as update my
> GCC repo with subversion and Mozilla with cvs. I realize that running
> Fedora Rawhide means when things break I can keep the pieces, so
> the lockups or other occasional issues are not unexpected.

I don't know the numbers of this kernels, but did you try 
linux-2.6.18-rc2.

It has some great patch to queue scheduler by Hubert Xu. I think 
it is some Gnu/miracle that it has been working (mostly) under 
heavy load without this patch.

But there are also other possibilities...

Jarek P.

  parent reply	other threads:[~2006-07-28 14:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 18:19 Debugging kernel lockups during network activity Art Haas
2006-07-27 18:27 ` Stephen Hemminger
2006-07-28 14:39 ` Jarek Poplawski [this message]
2006-07-31 14:15   ` Jarek Poplawski

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=44CA218E.6040502@o2.pl \
    --to=jarkao2@o2.pl \
    --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).