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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Feb 2009 14:54:15 -0500
From:	Mark Hounschell <dmarkh@....rr.com>
To:	Andreas Herrmann <andreas.herrmann3@....com>
CC:	Borislav Petkov <borislav.petkov@....com>,
	Mark Hounschell <markh@...pro.net>,
	john stultz <johnstul@...ibm.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: PROBLEM: Can't boot a (HZ = 1000) kernel using an AMD Phenom-II
 processor

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@...ley:~> 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?

Regards
Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/