From: "David S. Miller" <davem@davemloft.net>
To: kloczek@rudy.mif.pg.gda.pl
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
aurora-sparc-devel@lists.auroralinux.org, davem@redhat.com
Subject: Re: [2.6.14-rc1/sparc54]: BUG: soft lockup detected on CPU#0!
Date: Thu, 15 Sep 2005 13:30:26 -0700 (PDT) [thread overview]
Message-ID: <20050915.133026.21581824.davem@davemloft.net> (raw)
In-Reply-To: <Pine.BSO.4.62.0509151929580.5000@rudy.mif.pg.gda.pl>
From: Tomasz Kłoczko <kloczek@rudy.mif.pg.gda.pl>
Date: Thu, 15 Sep 2005 19:40:27 +0200 (CEST)
> I'm just catch series of kernel messages with soft lockup detected reports
> (in attachment).
> It occures during store big amout of data on NFS volume.
>
> As NIC I use now Sun Swift gigabit eth (cassini driver). Probably this is
> NFS related because I'm just browse yesterday logs and simillar was also
> on Sun Happy Meal.
Interesting. Can you reproduce this with SLAB poisioning disabled?
That debugging feature is extremely expensive, although it shouldn't
make the CPU stop scheduling processes for more than 10 seconds.
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.
I'll also try to see if there can be some kind of sparc64 specific
issue which would cause this.
Where did you get that Cassini driver btw? It's not upstream,
although if it exists it should be.
next prev parent reply other threads:[~2005-09-15 20:30 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 [this message]
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
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=20050915.133026.21581824.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aurora-sparc-devel@lists.auroralinux.org \
--cc=davem@redhat.com \
--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®