From: Jeremiah Mahler <jmmahler@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] linux-next: 20141127 boot hang
Date: Sat, 29 Nov 2014 01:15:10 -0800 [thread overview]
Message-ID: <20141129091510.GA1366@newt.localdomain> (raw)
In-Reply-To: <20141128233250.GA4921@hudson.localdomain>
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.
--
- Jeremiah Mahler
next prev parent reply other threads:[~2014-11-29 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141127231619.GA1713@hudson.localdomain>
2014-11-28 23:32 ` Jeremiah Mahler
2014-11-29 9:15 ` Jeremiah Mahler [this message]
2014-11-29 10:44 ` Stephen Rothwell
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=20141129091510.GA1366@newt.localdomain \
--to=jmmahler@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®