Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751538AbaK1Xcz (ORCPT ); Fri, 28 Nov 2014 18:32:55 -0500 Received: from mail-pa0-f42.google.com ([209.85.220.42]:61883 "EHLO mail-pa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751256AbaK1Xcy (ORCPT ); Fri, 28 Nov 2014 18:32:54 -0500 Date: Fri, 28 Nov 2014 15:32:50 -0800 From: Jeremiah Mahler To: Stephen Rothwell Cc: linux-kernel@vger.kernel.org Subject: Re: [BUG] linux-next: 20141127 boot hang Message-ID: <20141128233250.GA4921@hudson.localdomain> Mail-Followup-To: Jeremiah Mahler , Stephen Rothwell , linux-kernel@vger.kernel.org References: <20141127231619.GA1713@hudson.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141127231619.GA1713@hudson.localdomain> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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. -- - Jeremiah Mahler -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/