| 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
| ||
|
Date: Mon, 08 Dec 2008 18:14:00 -0800 From: john stultz <johnstul@...ibm.com> To: Harald Dunkel <harald.dunkel@...nline.de> Cc: Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: 2.6.27.7 built for Geode: Clock drift On Sat, 2008-12-06 at 07:09 +0100, Harald Dunkel wrote: > john stultz wrote: > > > > For both configs, can you run: > > cat /sys/devices/system/clocksource/clocksource0/available_clocksource > > and: > > cat /sys/devices/system/clocksource/clocksource0/current_clocksource > > > > Then send back the output? > > > > Sure. For 486: > > % cat /sys/devices/system/clocksource/clocksource0/available_clocksource > pit jiffies > % cat /sys/devices/system/clocksource/clocksource0/current_clocksource > pit > > > For Geode (clock is running too fast): > % cat /sys/devices/system/clocksource/clocksource0/available_clocksource > jiffies > % cat /sys/devices/system/clocksource/clocksource0/current_clocksource > jiffies > > > dmesg says for Geode: > > : > TSC: Unable to calibrate against PIT > TSC: No reference (HPET/PMTIMER) available > Marking TSC unstable due to could not calculate TSC khz Could you send your .config? It seems the PIT (which is used in 486 build) is being disabled in the Geode config. However, I thought the Geode's had their own clocksources, either the SCx200 or the GEODE_MFGPT_TIMER. Maybe one of those needs to be enabled? thanks -john -- 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