From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED][X86] next-20080526 hangs on boot
Date: Mon, 26 May 2008 18:41:34 +0400 [thread overview]
Message-ID: <20080526144134.GA7305@cvg> (raw)
In-Reply-To: <g1eg2q$81q$1@ger.gmane.org>
[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@gmail.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@gmail.com>
| Cc: hpa@zytor.com
| Cc: mingo@redhat.com
| Signed-off-by: Thomas Gleixner <tglx@linutronix.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 -
next prev parent reply other threads:[~2008-05-26 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 14:04 [REGRESSION][BISECTED][X86] next-20080526 hangs on boot Sitsofe Wheeler
2008-05-26 14:41 ` Cyrill Gorcunov [this message]
2008-05-26 16:16 ` Cyrill Gorcunov
2008-05-26 19:11 ` Sitsofe Wheeler
2008-05-26 19:36 ` Sitsofe Wheeler
2008-05-26 19:44 ` Cyrill Gorcunov
2008-05-27 6:35 ` Cyrill Gorcunov
2008-05-27 22:16 ` Sitsofe Wheeler
2008-05-27 22:50 ` Adrian Bunk
2008-05-28 3:21 ` Cyrill Gorcunov
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=20080526144134.GA7305@cvg \
--to=gorcunov@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@yahoo.com \
/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