From: Chuck Ebbert <cebbert@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Prakash Punnoor <prakash@punnoor.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Why do so many machines need "noapic"?
Date: Mon, 10 Sep 2007 19:33:30 -0400 [thread overview]
Message-ID: <46E5D44A.5000201@redhat.com> (raw)
In-Reply-To: <20070910194421.GA1819@one.firstfloor.org>
On 09/10/2007 03:44 PM, Andi Kleen wrote:
>> 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.)
>
> x86-64 has quite different time code (at least until the dyntick patches
> currently in mm)
>
> Obvious thing would be to diff the boot messages and see if anything
> jumps out (e.g. in interrupt routing).
>
> Or check with mm and if x86-64 is broken there too then it's likely
> the new time code.
This is Fedora 8 and it already has the highres-timers code in x86_64.
But I was still comparing 2.6.22 on i386 to 2.6.23-rc5-git1 + highres-timers
on x86_64. 2.6.23-rc5 on i386 seems okay too, so whatever is happening it
only occurs on 2.6.22 here.
next prev parent reply other threads:[~2007-09-10 23:33 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
2007-09-10 19:44 ` Andi Kleen
2007-09-10 23:33 ` Chuck Ebbert [this message]
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=46E5D44A.5000201@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 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.