From: john stultz <johnstul@us.ibm.com>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-kernel@vger.kernel.org, bunk@stusta.de, jikos@jikos.cz,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [BUG] no boot with 2.6.21-rc3 and later
Date: Thu, 22 Mar 2007 12:56:42 -0700 [thread overview]
Message-ID: <1174593402.5662.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20070322193946.2B7D8DBA1@gherkin.frus.com>
On Thu, 2007-03-22 at 13:39 -0600, Bob Tracy wrote:
> john stultz wrote:
> > On Thu, 2007-03-22 at 13:14 -0600, Bob Tracy wrote:
> > > john stultz wrote:
> > > > Try this patch and let me know if it does the right thing.
> > >
> > > Will do. I'll report back in a few hours.
> > >
> > > > Although I do
> > > > still need to dig a bit on the PIT hang issue.
> > >
> > > Any chance this might be related to the APIC issues currently being
> > > discussed in other threads?
> >
> > Hmmm. Good thought, I'll have to look into it. It could be that if the
> > PIT is disabled in favor of the local apic, we'll have to make sure its
> > not being used as a clocksource.
>
> According to the dmesg output, the local apic is disabled in the BIOS on
> this system, and I'm not booting with "lapic" to enable it.
>
> Anyway, the "few hours" turned out to be more like a few minutes :-).
> The patch worked as far as selecting/installing the acpi_pm clocksource
> instead of the pit clocksource, and there was no hang during boot. If
> you would like to see the dmesg output, let me know and I'll forward it
> to you in a separate message.
Great to hear! Please do send me the dmesg output so I can look to
narrow down what's happening w/ the PIT.
I'll also go ahead and push that acpi_pm change to akpm.
thanks
-john
next prev parent reply other threads:[~2007-03-22 19:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 19:54 [BUG] no boot with 2.6.21-rc3 and later Bob Tracy
2007-03-21 20:18 ` Bartlomiej Zolnierkiewicz
2007-03-21 21:34 ` john stultz
2007-03-21 22:00 ` Bob Tracy
2007-03-21 22:24 ` john stultz
2007-03-22 3:45 ` Bob Tracy
2007-03-22 18:35 ` john stultz
2007-03-22 19:14 ` Bob Tracy
2007-03-22 19:25 ` john stultz
2007-03-22 19:39 ` Bob Tracy
2007-03-22 19:56 ` john stultz [this message]
2007-03-22 20:13 ` Bob Tracy
2007-03-22 19:43 ` Thomas Gleixner
2007-03-22 20:25 ` [PATCH] correct slow acpi_pm rating (fixes no boot with 2.6.21-rc3 and later) john stultz
-- strict thread matches above, loose matches on Subject: below --
2007-03-20 1:43 [BUG] no boot with 2.6.21-rc3 and later Bob Tracy
2007-03-20 7:14 ` Jiri Kosina
2007-03-18 1:09 Bob Tracy
2007-03-18 18:59 ` Jiri Kosina
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=1174593402.5662.10.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=bunk@stusta.de \
--cc=bzolnier@gmail.com \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rct@gherkin.frus.com \
--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