Messages in this thread | | | Date | 28 Aug 2006 08:13:02 +0200 | Date | Mon, 28 Aug 2006 08:13:02 +0200 | From | Andi Kleen <> | Subject | Re: Linux v2.6.18-rc5 |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |