From: "Ted Ts'o" <tytso@mit.edu>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 3.3.0-rcX: kjournald
Date: Tue, 21 Feb 2012 07:42:40 -0500 [thread overview]
Message-ID: <20120221124240.GB5134@thunk.org> (raw)
In-Reply-To: <20120221054159.GA1919@gherkin.frus.com>
On Mon, Feb 20, 2012 at 11:41:59PM -0600, Bob Tracy wrote:
> I'm not sure if I caught a complete instance of this in "syslog", but
> here's what I've been seeing with 3.3.0-rc[1-3] kernels. Shortly after
> booting multi-user, logging in, and attempting a package build, the
> "fun" starts: the following message scrolls repeatedly (possibly with
> different details) across the console. To date, I've had to hit the
> reset switch to recover, which is why I'm not sure whether I caught a
> complete syslog entry.
Hmm.. I've taken a quick look at fs/jbd/commit.c, and I don't see
anything obvious. Can you try compiling with LOCKDEP compiled and see
if you can reproduce it, so we can see what spin lock is being held?
Thanks,
- Ted
next prev parent reply other threads:[~2012-02-21 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 5:41 [BUG] 3.3.0-rcX: kjournald Bob Tracy
2012-02-21 12:42 ` Ted Ts'o [this message]
2012-02-23 3:55 ` Bob Tracy
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=20120221124240.GB5134@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rct@gherkin.frus.com \
/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