linux-kernel - Re: X fails to start with latest Linus git

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]

Message-Id: <20080127191238.92d95770.kjwinchester@gmail.com>
Date:	Sun, 27 Jan 2008 19:12:38 -0400
From:	Kevin Winchester <kjwinchester@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	John Stultz <johnstul@...ibm.com>
Subject: Re: X fails to start with latest Linus git

On Sun, 27 Jan 2008 13:42:44 +0100
Ingo Molnar <mingo@...e.hu> wrote:

> 
> * Ingo Molnar <mingo@...e.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.
> 

Ok, I'll try disabling cpufreq to see if that prevents the lockup.  If
that is the problem, what is the fix?  Just to keep the path reverted?

-- 
Kevin Winchester <kjwinchester@...il.com>
--
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/