| 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
| ||
|
Message-Id: <20080127191033.b883c595.kjwinchester@gmail.com> Date: Sun, 27 Jan 2008 19:10:33 -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> Subject: Re: X fails to start with latest Linus git On Sun, 27 Jan 2008 13:37:02 +0100 Ingo Molnar <mingo@...e.hu> wrote: > > * Kevin Winchester <kjwinchester@...il.com> wrote: > > > Sure, the result of the script is at > > > > http://personal.nbnet.nb.ca/kwin/cfs-debug-info-2008.01.27-08.13.28 > > it seems you've got hpet active by default: > > /sys/devices/system/clocksource/clocksource0/current_clocksource: > hpet > /sys/devices/system/clocksource/clocksource0/available_clocksource: > hpet acpi_pm pit jiffies tsc > > do you get a similar lockup if you use acpi_pm? You can do that either > by disabling the HPET options in your .config, or by doing this prior > starting up X: > > echo acpi_pm > /sys/devices/system/clocksource/clocksource0/current_clocksource > Since X was being autostarted when the computer booted, I just removed "hpet=force" from my command line instead. The result was that the lockup happened earlier, so that it was before X was being started. So I guess X is not the culprit. -- 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/
Powered by blists - more mailing lists