mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: kloczek@rudy.mif.pg.gda.pl
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
	sparclinux@vger.kernel.org,
	aurora-sparc-devel@lists.auroralinux.org
Subject: Re: [2.6.14-rc1/sparc54]: BUG: soft lockup detected on CPU#0!
Date: Fri, 16 Sep 2005 15:59:19 -0400 (EDT)	[thread overview]
Message-ID: <20050916.155919.41629794.davem@redhat.com> (raw)
In-Reply-To: <Pine.BSO.4.62.0509161405550.5000@rudy.mif.pg.gda.pl>

From: Tomasz Kłoczko <kloczek@rudy.mif.pg.gda.pl>
Date: Fri, 16 Sep 2005 14:42:56 +0200 (CEST)

> On Thu, 15 Sep 2005, David S. Miller wrote:
> 
> > I wonder if the NFS daemon code needs to have some limits put on
> > how much cpu it consumes handling requests before it gives up the
> > cpu.  Perhaps, it has such throttling already, I don't know.
> 
> But this not case NFS server but NSF client. During this lookups I observe 
> rpciod takes 90-99% time of single processor. Load is between 10 and 20.

After studying some code yesterday, NFS client has the same
exact problem as NFS daemon, namely that if you give it enough
work it will never give up the cpu so that other tasks can
be scheduled.

This is a serious bug, and can easily trigger those soft lockup
messages.  Based upon some other reports seen on linux-kernel
and elsewhere, things like the raid1 kernel daemon have a similar
issue as well.

I think you can help things _enormusly_ by turning off SLAB
poisioning, as I said that debugging feature is _VERY_ expensive.

  parent reply	other threads:[~2005-09-16 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15 17:40 Tomasz Kłoczko
2005-09-15 20:30 ` David S. Miller
2005-09-15 20:36   ` Jima
2005-09-16 12:42   ` Tomasz Kłoczko
2005-09-16 19:57     ` David S. Miller
2005-09-16 19:59     ` David S. Miller [this message]
2005-09-17 15:22       ` Tomasz Kłoczko
2005-09-17 17:49         ` Tomasz Kłoczko
2005-09-18  6:45           ` David S. Miller

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=20050916.155919.41629794.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=aurora-sparc-devel@lists.auroralinux.org \
    --cc=davem@davemloft.net \
    --cc=kloczek@rudy.mif.pg.gda.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@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

all inboxes | Powered by JetHome®