public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Drake <zappacky.lists@gmail.com>
To: Glauber Costa <glommer@gmail.com>
Cc: linux-kernel@vger.kernel.org, gcosta@redhat.com
Subject: Re: [Bisected] Regression: Hang on boot in schedule_timeout_interruptible during ACPI init on SMP
Date: Sat, 26 Jul 2008 14:53:11 -0400	[thread overview]
Message-ID: <488B7297.8090405@gmail.com> (raw)
In-Reply-To: <5d6222a80807231731u41f9fb81w2796b3db1a5920e6@mail.gmail.com>

I just discovered; the nolapic_timer parameter causes the problem to go away 
entirely. It doesn't seem to have any nasty side effects, so I'm content to use 
it. Looking at the dmesg logs, however, I notice that the "last-good" kernel 
doesn't even try to use the LAPIC timer, but the "first-bad" does. I wasn't able 
to track down any discernible reason.

On a side note, that's the first I've ever heard/seen of that parameter, I tried 
it because I noticed the problems started when the LAPIC timer was successfully 
set up. I doubt the average user would notice this (you can't even tell unless 
you pass apic=debug), so I doubt many others would discover this fix/workaround.

The question remains, though, why did it go from "don't try" to "try"?

Thanks,

Andrew


  parent reply	other threads:[~2008-07-26 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 22:46 [Bisected] Regression: Hang on boot in schedule_timeout_interruptible during ACPI init on SMP Andrew Drake
2008-07-24  0:31 ` Glauber Costa
2008-07-24 22:54   ` Andrew Drake
2008-07-26 18:53   ` Andrew Drake [this message]
2008-07-28 14:15     ` Glauber Costa
2008-07-28 14:59       ` Glauber Costa
2008-07-28 16:46       ` Andrew Drake
2008-07-28 18:24         ` Glauber Costa

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=488B7297.8090405@gmail.com \
    --to=zappacky.lists@gmail.com \
    --cc=gcosta@redhat.com \
    --cc=glommer@gmail.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