From: Jan Kara <jack@suse.cz>
To: Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>
Cc: jack@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: Soft lockup problem
Date: Wed, 8 Feb 2012 10:23:31 +0100 [thread overview]
Message-ID: <20120208092331.GA24625@quack.suse.cz> (raw)
In-Reply-To: <20120207231615.11358.qmail@md.dent.med.uni-muenchen.de>
On Wed 08-02-12 00:16:15, Wolfram Gloger wrote:
> Thanks for your response.
>
> > From: Jan Kara <jack@suse.cz>
>
> > Hmm, then this isn't really a deadlock (at least in your case) but only a
> > rather unresponsive system.
>
> Well, like the subject says this is a "soft lockup"..
We differ in terminology a bit but that's not really important when I
know what you mean :)
> When it happened the first time the system actually recovered
> after some hours.
> But like Gerard said, there is no apparent ground for this
> unresponsiveness, there are tons of memory free and no swapping.
Yeah, interesting. There are no processes waiting for IO either so I'm
puzzled what causes you problems.
> > Looking at the backtraces you provided I don't
> > see anything really suspicious. Only maybe fsnotify_mark process - do you
> > use fsnotify?
>
> I have configured CONFIG_FSNOTIFY=y indeed but don't think I'm using it
> from userspace..
Well, apparently something uses it because fsnotify_mark thread is just
in the process of destroying some mark. Maybe you could run with
CONFIG_FSNOTIFY=n just to rule out some problems there...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2012-02-08 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120207215737.10744.qmail@md.dent.med.uni-muenchen.de>
2012-02-07 22:52 ` Jan Kara
2012-02-07 23:16 ` Wolfram Gloger
2012-02-08 9:23 ` Jan Kara [this message]
2012-02-06 15:40 Gerard Saraber
2012-02-06 17:37 ` Gerard Saraber
2012-02-06 22:51 ` Jan Kara
2012-02-07 16:35 ` Gerard Saraber
2012-02-07 16:54 ` Jan Kara
2012-02-27 14:38 ` Gerard Saraber
[not found] ` <CAOgv-zjF3YSLuGu0p0xkCp5ZfWu2H1Xg8aQ7xcpCQqWOdwh1aA@mail.gmail.com>
2012-02-29 19:14 ` Jan Kara
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=20120208092331.GA24625@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=wmglo@dent.med.uni-muenchen.de \
/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
Powered by JetHome