linux-kernel - [BUG,2.6.29-rc7,s390] System goes into endless loop during boot or logon

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-next>] [day] [month] [year] [list]

Date:	Mon, 9 Mar 2009 02:53:32 +0100
From:	Frans Pop <elendil@...net.nl>
To:	linux-s390@...r.kernel.org
Cc:	Hendrik Brueckner <brueckner@...ux.vnet.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [BUG,2.6.29-rc7,s390] System goes into endless loop during boot or logon

Follow-up to an issue reported on the linux-s390 list, seen in the 
Hercules S/390 emulator.

On Sunday 08 March 2009, Frans Pop wrote:
> Well, not quite. It does boot successfully and I do get a login prompt.
> I can also login on the console or connect with SSH, but in both cases
> the system again gets into some loop before I actually get a shell
> prompt.

During the bisection series the system would sometimes enter the loop 
during the boot procedure, before I tried to logon. After it enters the 
loop one processor just goes racing at 100%.

I've bisected this to the following set of three patches:
commit ca109491f612aab5c8152207631c0444f63da97f
Author: Peter Zijlstra <peterz@...radead.org>
Date:   Tue Nov 25 12:43:51 2008 +0100
    hrtimer: removing all ur callback modes
commit 37810659ea7d9572c5ac284ade272f806ef8f788
    hrtimer: removing all ur callback modes, fix hotplug
commit a0a99b227da57f81319dd239bc4de811b0f530ec
    hrtimer: removing all ur callback modes, fix

I've not tried to bisect between these patches as the last two are fixes. 
If needed I can do though.

Unfortunately I was unable to revert that series on top of .29-rc7.

Note:
During the bisect I had to revert 3 other commits before each iteration 
because of issues already present in 2.6.28 (reported separately):
commit 49b5cf34727a6c1be1568ab28e89a2d9a6bf51e0
commit 5cd1c9c5cf30d4b33df3d3f74d8142f278d536b7
commit 6c9bacb41c10ba84ff68f238e234d96f35fb64f7

Cheers,
FJP


View attachment "config" of type "text/plain" (26464 bytes)