From: Jordan Russell <jr-list-2007@quo.to>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
john stultz <johnstul@us.ibm.com>
Subject: Re: 2.6.23.1: Random hangs during boot with "tsc" clocksource
Date: Fri, 23 Nov 2007 12:29:13 -0600 [thread overview]
Message-ID: <47471BF9.8020100@quo.to> (raw)
In-Reply-To: <47446690.5090808@redhat.com>
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@issp.bas.bg>
> To: linux-kernel@vger.kernel.org
> Subject: [PATCH]new_TSC_based_delay_tsc()
> Cc: Ingo Molnar <mingo@elte.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
prev parent reply other threads:[~2007-11-23 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 17:10 2.6.23.1: Random hangs during boot with "tsc" clocksource Jordan Russell
2007-11-07 6:15 ` Andrew Morton
2007-11-20 23:20 ` Jordan Russell
2007-11-21 17:10 ` Chuck Ebbert
2007-11-23 18:29 ` Jordan Russell [this message]
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=47471BF9.8020100@quo.to \
--to=jr-list-2007@quo.to \
--cc=akpm@linux-foundation.org \
--cc=cebbert@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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