linux-next: 20141127 boot hang
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Jeremiah Mahler
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 <[email protected]>
Date: Thu Nov 27 14:53:44 2014 +1100
Merge remote-tracking branch 'block/for-next'
Conflicts:
fs/fs-writeback.c
I will continue until I find the specific patch.
Signature · 1 line
- Jeremiah Mahler
all,
Quoted 18 lines · Jeremiah Mahler
Quoted 7 lines · Jeremiah Mahler
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 <[email protected]>
Date: Thu Nov 27 14:53:44 2014 +1100
Quoted 5 lines
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.
Signature · 1 line
- Jeremiah Mahler
Hi Jeremiah,
Quoted 24 lines · On Sat, 29 Nov 2014 01:15:10 -0800 Jeremiah Mahler <[email protected]> wrote:
all,
Quoted 20 lines · Jeremiah Mahler
Quoted 7 lines · Jeremiah Mahler
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 <[email protected]>
Date: Thu Nov 27 14:53:44 2014 +1100Merge remote-tracking branch '
block/for-next'
Quoted 8 lines
Quoted 3 lines
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?
Signature · 2 lines
Cheers, Stephen Rothwell [email protected]