From: Glauber Costa <gcosta@redhat.com>
To: Andrew Drake <zappacky.lists@gmail.com>
Cc: Glauber Costa <glommer@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [Bisected] Regression: Hang on boot in schedule_timeout_interruptible during ACPI init on SMP
Date: Mon, 28 Jul 2008 11:15:33 -0300 [thread overview]
Message-ID: <20080728141533.GA3697@redhat.com> (raw)
In-Reply-To: <488B7297.8090405@gmail.com>
On Sat, Jul 26, 2008 at 02:53:11PM -0400, Andrew Drake wrote:
> 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.
fine, but if you can still help us on this, it would be awesome ;-)
Actually, there is another nasty bug that depends, at least by a first
impression, on the lapic timer. I'm planning to save a time today to
look further on your problem.
>
> 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"?
Probably because the order of initialization of smp entities changed a
bit during this series. Probably the lapic timer is now initialized a
little bit earlier, before we have the chance to mark it as bad.
If you can send me at least your dmesgs and cpuinfo, it would be really really
awesome.
> Thanks,
>
> Andrew
>
next prev parent reply other threads:[~2008-07-28 14:16 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
2008-07-28 14:15 ` Glauber Costa [this message]
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=20080728141533.GA3697@redhat.com \
--to=gcosta@redhat.com \
--cc=glommer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zappacky.lists@gmail.com \
/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