From: Ingo Molnar <mingo@elte.hu>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
John Stultz <johnstul@us.ibm.com>
Subject: Re: X fails to start with latest Linus git
Date: Sun, 27 Jan 2008 13:42:44 +0100 [thread overview]
Message-ID: <20080127124244.GA24999@elte.hu> (raw)
In-Reply-To: <20080127124120.GA23377@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> hm, perhaps it's due to the xtime lock dependency:
>
> do {
> seq = read_seqbegin(&xtime_lock);
> getnstimeofday(ts);
> tomono = wall_to_monotonic;
>
> } while (read_seqretry(&xtime_lock, seq));
>
> perhaps your system somehow generates a printk from within an
> xtime_lock locked section?
i _bet_ it's these printks that cause your lockup:
[ 10.313437] Marking TSC unstable due to: cpufreq changes.
[ 10.313437] Time: hpet clocksource has been installed.
[ 10.424431] Clocksource tsc unstable (delta = -121609771 ns)
as these are done with the xtime lock held.
Ingo
next prev parent reply other threads:[~2008-01-27 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 0:19 X fails to start with latest Linus git Kevin Winchester
2008-01-27 0:35 ` Kevin Winchester
2008-01-27 6:27 ` Ingo Molnar
2008-01-27 10:42 ` Jan Engelhardt
2008-01-27 12:31 ` Kevin Winchester
2008-01-27 12:35 ` Ingo Molnar
2008-01-27 23:08 ` Kevin Winchester
2008-01-27 12:37 ` Ingo Molnar
2008-01-27 12:41 ` Ingo Molnar
2008-01-27 12:42 ` Ingo Molnar [this message]
2008-01-27 23:12 ` Kevin Winchester
2008-01-27 23:35 ` Kevin Winchester
2008-01-27 23:10 ` Kevin Winchester
2008-01-27 7:12 ` [git pull] printk fix (was: Re: X fails to start with latest Linus git) Ingo Molnar
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=20080127124244.GA24999@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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