Re: lockups shortly after booting in current git.

Dave Jones
2012-03-29T21:12:54Z

On Thu, Mar 29, 2012 at 01:59:33PM -0700, Linus Torvalds wrote:
> On Thu, Mar 29, 2012 at 1:39 PM, Ted Ts'o <tytso@mit.edu> wrote:
> >
> > 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.
>
> Ahh, that does sound interesting and relevant.
>
> Yeah, maybe the directed approach is worth it. In fact, considering
> the above commie, maybe it might be worth it to be *very* directed,
> and just test that one thing first, and maybe even skip the bisection
> entirely and just test a revert if it looks promising.

I'll try a build with just that reverted, given the bisect build is taking a while.

Any thoughts on any printk's I could add to verify a situation occurred or not ?
The problem with bisecting a bug like this is that it's hard to tell if
the bug has been fixed, or if I've just not hit it yet.

Dave