Re: PROBLEM: Can't boot a (HZ = 1000) kernel using an AMD Phenom-II processor

Mark Hounschell
2009-02-20T20:27:36Z

Mark Hounschell wrote:
> Mark Hounschell wrote:
>> Andreas Herrmann wrote:
>>> On Fri, Feb 20, 2009 at 12:40:31PM -0500, Mark Hounschell wrote:
>>>
>>>> ACPI: HPET id: 0x10b9a201 base: 0xfed00000
>>> <snip>
>>>
>>>> hpet: hpet_enable(834):
>>>> hpet: ID: 43538301, PERIOD: 429b17e
>>> This means that your BIOS could be bogus.
>>> Obviously ACPI HPET table contains different information about
>>> your HPET configuration than the HPET registers are showing.
>>>
>>> This means that other chipset configuration (e.g. ACPI tables) could
>>> also be wrong.
>>>
>>> To confirm this please provide us output of
>>>
>>> # xxd /sys/firmware/acpi/tables/HPET
>> markh@harley:~> xxd /sys/firmware/acpi/tables/HPET
>> 0000000: 4850 4554 3800 0000 0101 5258 3738 3020 HPET8.....RX780
>> 0000010: 4157 5244 4143 5049 312e 3042 4157 5244 AWRDACPI1.0BAWRD
>> 0000020: 9800 0000 01a2 b910 0000 0000 0000 d0fe ................
>> 0000030: 0000 0000 0010 0000
>>
>> Mark
>>
>
> I don't intend to sound stupid but isn't this a _read only_ HPET ID register,
> read by the BIOS and put in a table which ends up being read by the kernel then
> in turn put in /sys/firmware/acpi/tables/HPET? If it is correct there, doesn't
> that mean the BIOS read it correctly and it is correct? And in turn, mean that
> the function used to read it for your debug printk could just be reading it wrong?
>
> Also remember in the beginning of this thread this machine was running on a
> Phenom-I and when I put a Phenom II in it I could no longer boot a 1000Hz
> kernel. I know, that often means nothing. But not always???
>
> I still have that original Phenom available and it is in another very similar
> BIOSTAR motherboard TA770 A2+ SE and is running a 1000Hz kernel. The MB does
> have a different BIOS mfgr however. Would it be of any benefit to do any of
> these things on that machine?
>
>

Ok I sounded stupid anyway. Its the ACPI: HPET id: 0x10b9a201 base: 0xfed00000
that is incorrect? I'll be quiet and wait.

Mark