linux-kernel - Re: Long timeout when booting >= 2.6.38

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: <4DBF1725.3030800@christianhoffmann.info>
Date:	Mon, 02 May 2011 22:42:13 +0200
From:	Christian Hoffmann <email@...istianhoffmann.info>
To:	john stultz <johnstul@...ibm.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Long timeout when booting >= 2.6.38

Hi,

> Hrm. So, on older kernels, what do you see from:
> $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> $ cat /sys/devices/system/clocksource/clocksource0/available_clocksource

On older and newer kernel I see the same output:
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
$ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
tsc hpet acpi_pm

>
> Hrm. The delay in the dmesg logs doesn't really seem to correlate that
> closely with the delayed tsc calibration. Hrmm..
>

Maybe some side effect somehow. I can't explain.

Rgds,
Chris
--
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/