public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Hoffmann <email@christianhoffmann.info>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: john stultz <johnstul@us.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Long timeout when booting >= 2.6.38
Date: Wed, 04 May 2011 21:40:11 +0200	[thread overview]
Message-ID: <4DC1AB9B.8080501@christianhoffmann.info> (raw)
In-Reply-To: <alpine.LFD.2.02.1105041931510.3005@ionos>

>
> Hmm. So I really wonder why it refuses to switch to acpi_pm when you
> select it on the kernel command line.
>
> Does "echo acpi_pm>  /sys/devices/system/clocksource/clocksource0/current_clocksource"
> work ?

Yes, that seems to work:

root@c3po:~# echo acpi_pm > 
/sys/devices/system/clocksource/clocksource0/current_clocksource
root@c3po:~# dmesg | grep clocksource
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-2.6.39-rc5-ch+ 
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+ 
root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 clocksource=acpi_pm
[    1.463754] Switching to clocksource tsc
[    1.470700] Override clocksource acpi_pm is not HRT compatible. 
Cannot switch while in HRT/NOHZ mode
[  125.808622] Switching to clocksource acpi_pm

>
> Ok. That excludes HPET. So the only difference left is the late
> registration of TSC which happens _AFTER_ the hang.
>
> Can you boot the non working kernel with "lpj=28098860" on the kernel
> command line ?

The dmesg output with lpj is here (and it still hangs):

http://pastebin.com/raw.php?i=wZWrbc7Z

Kind regards,

Chris

  reply	other threads:[~2011-05-04 19:40 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
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 [this message]
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=4DC1AB9B.8080501@christianhoffmann.info \
    --to=email@christianhoffmann.info \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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