From: Chuck Ebbert <cebbert@redhat.com>
To: Prakash Punnoor <prakash@punnoor.de>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Why do so many machines need "noapic"?
Date: Mon, 10 Sep 2007 15:12:22 -0400 [thread overview]
Message-ID: <46E59716.6020404@redhat.com> (raw)
In-Reply-To: <200709080717.58271.prakash@punnoor.de>
On 09/08/2007 01:17 AM, Prakash Punnoor wrote:
> On the day of Friday 07 September 2007 Chuck Ebbert hast written:
>> On 09/06/2007 07:31 AM, Andi Kleen wrote:
>>> Chuck Ebbert <cebbert@redhat.com> writes:
>>>> Some systems lock up without the noapic option.
>>> Please find patterns: cpu type, chipsets, mainboard vendors etc.
>> This is the first one I've actually had in front of me:
>>
>> HP TX1000 notebook
>> Nvidia C51/MCP51 mobile chipset
>
> Do you have a hpet? If not, have you tried using acpi_use_timer_override with
> apic?
Yes, it has an hpet. And I tried every combination of options I could
think of.
But, even stranger, x86_64 works (only i386 fails.)
next prev parent reply other threads:[~2007-09-10 19:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 23:30 Why do so many machines need "noapic"? Chuck Ebbert
2007-09-06 11:31 ` Andi Kleen
2007-09-07 19:34 ` Chuck Ebbert
2007-09-08 5:17 ` Prakash Punnoor
2007-09-10 19:12 ` Chuck Ebbert [this message]
2007-09-10 19:44 ` Andi Kleen
2007-09-10 23:33 ` Chuck Ebbert
2007-09-13 16:38 ` Chuck Ebbert
2007-09-25 9:06 ` Thomas Gleixner
2007-09-15 7:39 ` Andrew Morton
2007-09-15 10:58 ` Ingo Oeser
2007-09-15 11:08 ` Andrew Morton
2007-09-15 12:08 ` Matthew Garrett
2007-09-24 21:32 ` Dave Jones
2007-09-27 22:03 ` Phillip Susi
2007-09-15 18:42 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2007-09-08 4:12 Al Boldi
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=46E59716.6020404@redhat.com \
--to=cebbert@redhat.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prakash@punnoor.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