From: "David S. Miller" <davem@davemloft.net>
To: rdunlap@xenotime.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: soft lockup disease (2.6.14-rc1, x86_64)
Date: Thu, 15 Sep 2005 21:55:27 -0700 (PDT) [thread overview]
Message-ID: <20050915.215527.42819293.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0509151441430.1800@shark.he.net>
From: "Randy.Dunlap" <rdunlap@xenotime.net>
Date: Thu, 15 Sep 2005 15:20:03 -0700 (PDT)
> (somewhat like http://bugzilla.kernel.org/show_bug.cgi?id=5159 )
> but not IO/Storage related AFAICT, and not xseries.
>
> It always includes ext3 in the backtrace (from what I have noticed).
> [The serial console output appears a bit garbled.]
>
> Are there patches for this or is it an outstanding issue?
I've seen similar triggers on sparc64 from a reporter, but
it was NFSD and slab poisioning in the backtrace in that case.
I think the common denominator is the presence of very busy kernel
daemons unable to schedule out to let other tasks (and in particular
the per-cpu softlockup daemon) onto the cpu.
Looking at KNFSD specifically, I don't see anywhere that it tries to
yield the cpu if it's been working for too long.
I guess that's exactly what the softlockup thing was meant to catch
:-)
prev parent reply other threads:[~2005-09-16 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 22:20 Randy.Dunlap
2005-09-16 4:55 ` David S. Miller [this message]
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=20050915.215527.42819293.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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®