[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080526144134.GA7305@cvg>
Date: Mon, 26 May 2008 18:41:34 +0400
From: Cyrill Gorcunov <gorcunov@...il.com>
To: Sitsofe Wheeler <sitsofe@...oo.com>
Cc: linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org
Subject: Re: [REGRESSION][BISECTED][X86] next-20080526 hangs on boot
[Sitsofe Wheeler - Mon, May 26, 2008 at 03:04:54PM +0100]
| <posted & mailed>
|
| When using a 32 bit linux-next-20080526 the bootup process will hang at a
| random point (not even sysrq helps) with no additional output on the screen
| (whereas linux-next-20080523 did boot). Mysteriously, booting with
| nmi_watchdog=2 allows the boot to finish (booting with nmi_watchdog=1 still
| stalls). I have bisected it down to commit
| [d1b946b97d71423f365fa797d1428e1847c0bec1]:
|
| commit d1b946b97d71423f365fa797d1428e1847c0bec1
| Author: Cyrill Gorcunov <gorcunov@...il.com>
| Date: Sat May 24 19:36:34 2008 +0400
|
| x86: nmi_32.c - add "panic" option
|
| Allow to pass "panic" option in 32bit mode
|
| Signed-off-by: Cyrill Gorcunov <gorcunov@...il.com>
| Cc: hpa@...or.com
| Cc: mingo@...hat.com
| Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
|
| Reverting this seemed to allow the boot to proceed without issue. Here is
| the bisection log:
|
Hi, so it helps by reverting _only_ that commit? I mean all further commits
are still appiled?
- Cyrill -
--
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