linux-kernel - Re: 2.6.23.1: Random hangs during boot with "tsc" clocksource

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

Message-ID: <47471BF9.8020100@quo.to>
Date:	Fri, 23 Nov 2007 12:29:13 -0600
From:	Jordan Russell <jr-list-2007@....to>
To:	Chuck Ebbert <cebbert@...hat.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, john stultz <johnstul@...ibm.com>
Subject: Re: 2.6.23.1: Random hangs during boot with "tsc" clocksource

Chuck Ebbert wrote:
> On 11/20/2007 06:20 PM, Jordan Russell wrote:
>> Same problem with 2.6.23.8.
>>
>> Are there any specific (TSC related?) patches I should try reverting?
>>
>> Would it help if I captured the dmesg/SysRq output from one of the
>> hanging boots?
>>
>> Any other information that might be useful in getting to the bottom of this?
>>
> 
> Did you try this one? You are seeing problems with preemption disabled,
> but it's at least worth trying.
> 
> 
> 
> From: Marin Mitov <mitov@...p.bas.bg>
> To: linux-kernel@...r.kernel.org
> Subject: [PATCH]new_TSC_based_delay_tsc()
> Cc: Ingo Molnar <mingo@...e.hu>
> Date: 	Tue, 20 Nov 2007 21:32:27 +0200

Thanks for the response.

I backported that patch to 2.6.23.8, but it didn't make a difference.

I also went ahead and tested 2.6.24-rc3 (with no changes to the existing
config settings):

With the new CPU_IDLE option set to "n", it still hangs, but much less
frequently than on 2.6.23.x. In 25 tries, there were 3 hangs, all after
"input: AT Translated Set 2 keyboard as /class/input/input0".

With CPU_IDLE set to "y", it didn't hang at all in 25 tries. However,
CPU_IDLE=y produces these additional messages, which may explain why:

Marking TSC unstable due to: TSC halts in idle.
...
Time: acpi_pm clocksource has been installed.

Not sure what else to try at this point...

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