lkml.org 
[lkml]   [2014]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [BUG] linux-next: 20141127 boot hang
Hi Jeremiah,

On Sat, 29 Nov 2014 01:15:10 -0800 Jeremiah Mahler <jmmahler@gmail.com> wrote:
>
> all,
>
> On Fri, Nov 28, 2014 at 03:32:50PM -0800, Jeremiah Mahler wrote:
> > On Thu, Nov 27, 2014 at 03:16:19PM -0800, Jeremiah Mahler wrote:
> > >
> > > I just tried the latest linux-next 20141127 (commit 3bcf494d225fd19) and
> > > it hangs very early in the boot sequence, after decompressing the kernel
> > > and after fsck (see attached screen shot). I have tried it with two
> > > different machines and they both have the same problem. It worked with
> > > version 20141126.
> > >
> > []
> >
> > My bisect results so far indicate that the bug was introduced by this
> > merge commit.
> >
> > commit 0305904a7416ced1358c5ff575e58135453bfc1d
> > Merge: 38a4751 2ef5864
> > Author: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Thu Nov 27 14:53:44 2014 +1100
> >
> > Merge remote-tracking branch 'block/for-next'
> >
> > Conflicts:
> > fs/fs-writeback.c
> >
> []
>
> Something is definitely broken at this merge commit. I haven't
> quite figured out how to bisect the patches inside the merge commit.
> Any suggestions are welcome.

It could easily actually be the merge itself. There was a conflict in
that merge that I fixed up as best I could and asked others to check
the resolution.

I know that Cristoph thinks that the lazytime stuff is not ready for
-next yet, but are there any other comments?

--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2014-11-29 12:21    [W:0.050 / U:0.468 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site