public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Tracy <rct@gherkin.frus.com>
To: "Ted Ts'o" <tytso@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 3.3.0-rcX: kjournald
Date: Wed, 22 Feb 2012 21:55:51 -0600	[thread overview]
Message-ID: <20120223035551.GA2033@gherkin.frus.com> (raw)
In-Reply-To: <20120221124240.GB5134@thunk.org>

On Tue, Feb 21, 2012 at 07:42:40AM -0500, Ted Ts'o wrote:
> 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?

Was waiting for more specific instructions with respect to kernel config
options and how to use LOCKDEP (not familiar with it), and decided to
give 3.3.0-rc4 a try in the meantime.  Did NOT see the kjournald issue.

I guess I'll label this a "watch" item for now, unless something that
changed between -rc3 and -rc4 can be identified as the probable fix.

Thanks.
--Bob

      reply	other threads:[~2012-02-23  3:55 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
2012-02-23  3:55   ` Bob Tracy [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=20120223035551.GA2033@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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