public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Christian Hoffmann <email@christianhoffmann.info>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Long timeout when booting >= 2.6.38
Date: Mon, 02 May 2011 12:09:35 -0700	[thread overview]
Message-ID: <1304363375.3226.5.camel@work-vm> (raw)
In-Reply-To: <4DBEFCBA.3070501@christianhoffmann.info>

On Mon, 2011-05-02 at 20:49 +0200, Christian Hoffmann wrote:
> I have a strange hang/timeout when booting kernel 2.6.38 and newer. It 
> hangs after a few initialization steps and then after 145 seconds, it 
> continues to boot.
> 
> I bisected kernel and found that offensive revision is:
> 
> 08ec0c58fb8a05d3191d5cb6f5d6f81adb419798
> "x86: Improve TSC calibration using a delayed workqueue"
> 
> Older kernels before above revision work fine.
> 
> When passing acpi=off to kernel, the problem seems to disappear.

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 


> Dmesg output below where you can see the jump from 1.47 to 146.85.
> 
> The mainboard is an Asus M4A89GTD PRO/USB3 (latest BIOS revision).
> 
> Kind regards,
> Chris
> 
> PS: the problem has also been reported to ubuntu where more hw 
> information is attached.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765230
> PSS: dmesg output

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

thanks
-john



  reply	other threads:[~2011-05-02 19:10 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 [this message]
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
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=1304363375.3226.5.camel@work-vm \
    --to=johnstul@us.ibm.com \
    --cc=email@christianhoffmann.info \
    --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