public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Hoffmann <email@christianhoffmann.info>
To: john stultz <johnstul@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Long timeout when booting >= 2.6.38
Date: Wed, 04 May 2011 09:31:28 +0200	[thread overview]
Message-ID: <4DC100D0.1030302@christianhoffmann.info> (raw)
In-Reply-To: <1304470839.3037.12.camel@work-vm>

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

  reply	other threads:[~2011-05-04  7:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 18:49 Long timeout when booting >= 2.6.38 Christian Hoffmann
2011-05-02 19:09 ` john stultz
2011-05-02 20:42   ` Christian Hoffmann
2011-05-02 21:10     ` Christian Hoffmann
2011-05-02 22:12       ` john stultz
2011-05-02 21:49     ` john stultz
2011-05-02 22:27       ` Christian Hoffmann
2011-05-03  0:31         ` john stultz
2011-05-03 19:33           ` Christian Hoffmann
     [not found]           ` <4DC04E15.2030308@christianhoffmann.info>
2011-05-04  1:38             ` john stultz
2011-05-04  7:12               ` Christian Hoffmann
2011-05-04 17:04                 ` Christian Hoffmann
2011-05-04  1:00         ` john stultz
2011-05-04  7:31           ` Christian Hoffmann [this message]
2011-05-04  8:37             ` Thomas Gleixner
2011-05-04 16:47               ` Christian Hoffmann
2011-05-04 17:49                 ` Thomas Gleixner
2011-05-04 19:40                   ` Christian Hoffmann
2011-05-04 20:53                     ` Thomas Gleixner
2011-05-05 17:28                       ` Christian Hoffmann
2011-05-09  8:22                         ` Thomas Gleixner
2011-05-15 20:11                           ` Christian Hoffmann
2011-05-16  9:07                             ` Thomas Gleixner
2011-05-16 19:34                               ` Christian Hoffmann
2011-05-05  1:16             ` john stultz
2011-05-05  8:25               ` Thomas Gleixner
2011-05-05 17:47                 ` Christian Hoffmann
2011-05-05 18:41                   ` Thomas Gleixner
2011-05-03 18:12 ` David

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DC100D0.1030302@christianhoffmann.info \
    --to=email@christianhoffmann.info \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox