From: Glauber Costa <gcosta@redhat.com>
To: Andrew Drake <drakedevel.lists@gmail.com>
Cc: Andrew Drake <zappacky.lists@gmail.com>,
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 15:24:21 -0300 [thread overview]
Message-ID: <20080728182420.GB3697@redhat.com> (raw)
In-Reply-To: <2ae234c70807280946s77a02e1ex120fc2723e286a9e@mail.gmail.com>
On Mon, Jul 28, 2008 at 12:46:09PM -0400, Andrew Drake wrote:
> On Mon, Jul 28, 2008 at 10:15 AM, Glauber Costa <gcosta@redhat.com> wrote:
> > fine, but if you can still help us on this, it would be awesome ;-)
> >
>
> Oh absolutely! :P I'm not the type to settle on a workaround.
>
> > 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.
>
> Thanks!
>
> >
> > 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.
> >
>
> I noticed that; but I couldn't find where it was indeed marked as bad.
FYI: Bug 11101 (http://bugzilla.kernel.org/show_bug.cgi?id=11101) is probably
the same bug as yours. I've just updated a possible solution in there.
Could you verify that?
Thanks!
>
> > If you can send me at least your dmesgs and cpuinfo, it would be really really
> > awesome.
> >
>
> Did you get my most recent email? (It was sent to your glommer[at]
> address, and CC'd to the kernel list) If you didn't receive it, I'll
> forward you the message. It included dmesg of good kernel, dmesg of
> bad kernel, cpuinfo, .config, and my disassembled DSDT (which, as a
> side project, I'm doing a full-blown reverse engineering of).
>
> Thanks,
>
> Andrew
>
> P.S. I apologize in advance if this email is HTML, I'm at work and I
> have to use the gmail web interface, I have it set to "text only", but
> you never know.
prev parent reply other threads:[~2008-07-28 18:24 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
2008-07-28 14:59 ` Glauber Costa
2008-07-28 16:46 ` Andrew Drake
2008-07-28 18:24 ` Glauber Costa [this message]
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=20080728182420.GB3697@redhat.com \
--to=gcosta@redhat.com \
--cc=drakedevel.lists@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.