From: "Ted Ts'o" <tytso@mit.edu>
To: Dave Jones <davej@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lockups shortly after booting in current git.
Date: Thu, 29 Mar 2012 13:39:26 -0700 [thread overview]
Message-ID: <20120329203926.GA13970@thunk.org> (raw)
In-Reply-To: <20120329202619.GA14001@redhat.com>
On Thu, Mar 29, 2012 at 04:26:19PM -0400, Dave Jones wrote:
>
> I'll go back to trying the bisect now that I know how to reproduce it quickly.
> Do you think it might be worth restricting the bisect to fs/ ?
> Or shall I just do the whole tree bisect from 3.3 ?
I'd suggest restricting the bisect to fs/ first, and if that comes up
with something non-sensical, you can always use the good/bad data
points for a whole tree bisect.
One commit that you might want to try testing is b43d17f31^, and see
whether that works. One potential commit that might be suspicious is
b43d17f31 given the stack trace shows one process apparently waiting
on PageWriteback.
- Ted
next prev parent reply other threads:[~2012-03-29 20:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 15:55 lockups shortly after booting in current git Dave Jones
2012-03-29 18:23 ` Linus Torvalds
2012-03-29 18:29 ` Dave Jones
[not found] ` <CA+55aFxOcMt_mcr+ZYwc-SpKbROnh4Gn7jqrFY_SZcBy1Ev7Qw@mail.gmail.com>
[not found] ` <20120329182632.GA6891@redhat.com>
2012-03-29 18:36 ` Linus Torvalds
2012-03-29 19:53 ` Dave Jones
2012-03-29 20:10 ` Linus Torvalds
2012-03-29 20:26 ` Dave Jones
2012-03-29 20:38 ` Linus Torvalds
2012-03-29 20:39 ` Ted Ts'o [this message]
2012-03-29 20:59 ` Linus Torvalds
2012-03-29 21:12 ` Dave Jones
2012-03-29 21:45 ` Ted Ts'o
2012-03-29 21:49 ` Dave Jones
2012-03-29 21:52 ` Linus Torvalds
2012-03-29 22:54 ` Dave Jones
2012-03-29 23:04 ` Linus Torvalds
2012-03-29 23:35 ` Ted Ts'o
2012-03-29 23:25 ` Ted Ts'o
2012-03-29 21:52 ` Dave Jones
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=20120329203926.GA13970@thunk.org \
--to=tytso@mit.edu \
--cc=davej@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.