| 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: Thu, 26 Feb 2009 22:35:32 +0100 From: Jesper Krogh <jesper@...gh.cc> To: john stultz <johnstul@...ibm.com> CC: Linus Torvalds <torvalds@...ux-foundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Linux 2.6.29-rc6 john stultz wrote: > On Thu, Feb 26, 2009 at 12:43 PM, Jesper Krogh <jesper@...gh.cc> wrote: >> Linus Torvalds wrote: >>> On Thu, 26 Feb 2009, Jesper Krogh wrote: >>>> 2.6.26.8 doesnt have this problem. >>>> >>>> The "current_clocsource" is the same on both systems. >>>> >>>> $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource >>>> tsc >>> What does the frequency calibrate to? It should be in the dmesg. Does it >>> differ by a big amount? >> Non-working: >> $ dmesg | grep -i freq >> [ 0.004007] Calibrating delay loop (skipped), value calculated using >> timer frequency.. 4620.05 BogoMIPS (lpj=9240104) >> >> 2.6.26.8 doesn't have that information. > > I'm surprised the clocksource watchdog isn't catching it. > > What's the output from: > cat /sys/devices/system/clocksource/clocksource0/available_clocksource $ cat /sys/devices/system/clocksource/clocksource0/available_clocksource tsc acpi_pm jiffies Same on both. > Also mind sending the full dmesg for both kernels? http://krogh.cc/~jesper/dmesg-2.6.29-rc6.txt http://krogh.cc/~jesper/dmesg-2.6.26.8.txt -- Jesper -- 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