[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141129091510.GA1366@newt.localdomain>
Date: Sat, 29 Nov 2014 01:15:10 -0800
From: Jeremiah Mahler <jmmahler@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [BUG] linux-next: 20141127 boot hang
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@...b.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.
--
- Jeremiah Mahler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists