[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DC100D0.1030302@christianhoffmann.info>
Date: Wed, 04 May 2011 09:31:28 +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
On 05/04/2011 03:00 AM, john stultz wrote:
> On Tue, 2011-05-03 at 00:27 +0200, Christian Hoffmann wrote:
>>>
>>> Can you reproduce the hang booting with "clocksource=hpet" and
>>> "clocksource=acpi_pm" ?
>>
>> Both hang also.
>
> Sorry, one more clarifying point here:
>
> When you used either clocksource=hpet/clocksource=acpi_pm did the
> behavior of the system seem different after booting? In other words:
> does running time waiting a few seconds and then running time again show
> the expected passage of time? Were any following hangs seen, or was it
> only the first one at boot?
Hi,
with hpet no problems seen. No further hangs either.
In fact, switching to acpi_pm doesn't seem to work:
$ dmesg | grep clock
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-2.6.39-rc5-ch-broken+
root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 clocksource=acpi_pm
[ 0.000000] Kernel command line:
BOOT_IMAGE=/vmlinuz-2.6.39-rc5-ch-broken+ root=/dev/mapper/vg-root ro
quiet splash vt.handoff=7 clocksource=acpi_pm
[ 0.000000] hpet clockevent registered
[ 1.413835] Switching to clocksource hpet
[ 1.420762] Override clocksource acpi_pm is not HRT compatible.
Cannot switch while in HRT/NOHZ mode
[ 147.940143] Refined TSC clocksource calibration: 2809.409 MHz.
[ 147.940147] Switching to clocksource tsc
Regards,
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/
Powered by blists - more mailing lists