From: Andi Kleen <ak@muc.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Marc Perkel <marc@perkel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACurrid@nvidia.com, len.brown@intel.com
Subject: Re: Linux v2.6.18-rc5
Date: 28 Aug 2006 08:13:02 +0200 [thread overview]
Date: Mon, 28 Aug 2006 08:13:02 +0200 [thread overview]
Message-ID: <20060828061302.GA45823@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0608272246350.27779@g5.osdl.org>
On Sun, Aug 27, 2006 at 10:52:06PM -0700, Linus Torvalds wrote:
>
>
> On Sun, 27 Aug 2006, Marc Perkel wrote:
> >
> > You might want to look at this bug.
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=6975
> >
> > The current kernel doesn't run on Asus Motherboards that use the new AM2 CPUs.
That sounds like a overly broad statement. How do you know
it affects all Asus boards and not just your specific BIO version?
> > Should this be addressed before 2.6.18 is finished?
>
> Hmm. Can you verify that the system boots fine if you get rid of
> acpi_skip_timer_override as per the hint from Prakash Punnoor?
We already should disable it on NF5 automatically. Timer override was all
broken on NF3/NF4, but apparently works on NF5 again.
But the check relies on HPET being present. Maybe Asus "forgot"
to set up the HPET table again and the test fails.
[In general Asus BIOS writers seems to have issues. They completely
broke all the MCFG tables too]
I can't say from the URL above if it's that because it's missing a complete
boot log. Marc, please add that.
Andy, I guess the timer override check just needs to be tightened to check
the specific PCI IDs of NF3/NF4 only and not rely on HPET being right.
Do you have a list of them?
I suppose we also need a no_acpi_skip_override setup option for future
cases.
>
> Andi? You were talking about how the 64-bit machines don't have some of
> the cruft that the old PC's have.. It looks like they are accumulating
> _more_ cruft than regular x86 ever had...
Just by logic it's impossible because all 64bit systems are regular
PCs too @)
Anyways, there is cruft, but it is new cruft replacing the old cruft,
so overall there is less cruft.
-Andi
next prev parent reply other threads:[~2006-08-28 6:13 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 4:30 Linus Torvalds
2006-08-28 5:17 ` Marc Perkel
2006-08-28 5:52 ` Linus Torvalds
2006-08-28 6:13 ` Andi Kleen [this message]
2006-08-28 7:24 ` Prakash Punnoor
2006-08-28 12:05 ` Andi Kleen
2006-08-28 12:15 ` Prakash Punnoor
2006-08-28 16:02 ` Andi Kleen
2006-08-28 6:14 ` Andrew Morton
2006-08-28 6:19 ` Olaf Hering
2006-08-28 6:24 ` Andrew Morton
2006-08-28 14:41 ` Shailabh Nagar
2006-08-28 22:01 ` Shailabh Nagar
2006-08-28 6:29 ` Jeff Garzik
2006-08-28 7:25 ` Andi Kleen
2006-08-28 8:08 ` Thomas Gleixner
2006-08-28 17:20 ` Andrew Morton
2006-08-28 17:45 ` Thomas Gleixner
2006-08-28 8:05 ` Catalin Marinas
2006-08-28 8:25 ` Catalin Marinas
2006-08-28 8:34 ` Keith Owens
2006-08-28 8:42 ` Tejun Heo
2006-08-28 15:24 ` Keith Owens
2006-09-03 6:10 ` Tejun Heo
2006-09-06 6:42 ` Keith Owens
2006-09-13 14:41 ` Tejun Heo
2006-09-15 7:40 ` Keith Owens
2006-08-28 8:53 ` Beschorner Daniel
2006-08-28 15:26 ` Dmitry Torokhov
2006-08-29 2:01 ` Greg KH
2006-08-29 2:01 ` Greg KH
2006-08-29 14:50 ` Andreas Barth
2006-08-29 15:57 ` Brice Goglin
2006-08-30 15:54 ` Andrew Benton
2006-08-30 16:15 ` Takashi Iwai
2006-08-31 8:22 ` Takashi Iwai
2006-08-31 5:14 ` Len Brown
2006-09-02 1:40 ` Elias Holman
2006-09-02 1:50 ` Jeff Garzik
2006-08-28 10:10 ` Jesper Juhl
2006-08-28 10:27 ` Kasper Sandberg
2006-08-28 10:35 ` Jesper Juhl
2006-08-28 22:36 ` Nathan Scott
2006-08-28 23:30 ` Jesper Juhl
2006-08-30 8:14 ` Kasper Sandberg
2006-08-30 9:19 ` Jesper Juhl
2006-08-30 13:43 ` Jesper Juhl
2006-09-06 12:21 ` Paul Slootman
2006-08-28 13:04 ` Roger Luethi
2006-08-29 11:55 ` Olaf Hering
2006-08-29 13:06 ` Nathan Lynch
2006-08-29 15:52 ` Olaf Hering
2006-08-30 6:13 ` Paul Mackerras
2006-08-30 8:05 ` Olaf Hering
2006-08-30 9:00 ` Mikael Pettersson
2006-08-28 9:50 Chuck Ebbert
2006-08-28 18:40 ` Andrew Morton
2006-08-28 18:43 ` Arjan van de Ven
2006-08-29 5:36 Chuck Ebbert
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=20060828061302.GA45823@muc.de \
--to=ak@muc.de \
--cc=ACurrid@nvidia.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@perkel.com \
--cc=torvalds@osdl.org \
/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
Powered by JetHome