linux-kernel - Re: [REGRESSION][BISECTED][X86] next-20080526 hangs on boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 26 May 2008 20:11:53 +0100
From:	Sitsofe Wheeler <sitsofe@...oo.com>
To:	linux-kernel@...r.kernel.org
Cc:	kernel-testers@...r.kernel.org
Subject:  Re: [REGRESSION][BISECTED][X86] next-20080526 hangs on boot

<posted & mailed>

Cyrill Gorcunov wrote:

> [Sitsofe Wheeler - Mon, May 26, 2008 at 03:04:54PM +0100]
> | 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]:
>
> Hi, so it helps by reverting only that commit? I mean all further commits
> are still appiled?

Ah that I hadn't tested. I believe I might need to revert
4b82b277707a39b97271439c475f186f63ec4692 too if later commits are applied
(but I'm still testing)

> and, btw, could you post your config, please?

http://sucs.org/~sits/test/config-20080526.txt

-- 
Sitsofe | http://sucs.org/~sits/

--
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/