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, 06 Feb 2009 17:20:08 -0500
From:	Mark Hounschell <dmarkh@....rr.com>
To:	markh@...pro.net
CC:	Borislav Petkov <borislav.petkov@....com>,
	Andreas Herrmann <andreas.herrmann3@....com>,
	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:
>> Borislav Petkov wrote:
>>> Ok, here are two things you could try:
>>>
>>> Disable CONFIG_HIGH_RES_TIMERS (high resolution timers support in
>>> "Processor type and features"), boot with "apic=debug" and send me the
>>> output. I'd like to see how the lapic timer gets programmed. It would
>>> be better for that exercise to get the latest stable kernel, 2.6.28.3,
>>> imho.
>>>
>>> The other thing you could do is get x86info tools from here:
>>> http://www.codemonkey.org.uk/projects/x86info/. However, get either a
>>> daily snapshot or a checkout from the git repository and build it on
>>> your system. Then do
>>>
>>> x86info -a > x86info.txt
>>>
>>> lsmsr -V3 -a > lsmsr.txt
>>>
>>> and send me those text files - we might be able to get a clue what's going on
>>> from them.
> 
> Ok, attached is the bootlog.txt, x86info.txt, and lsmsr.txt
> 
> Thanks
> Mark
> 

That bootlog was captured from the serial console, but comparing it to the dmesg
I see more info in the dmesg. The extra stuff for "apic=debug" must not be going
to the serial console?? Either way here is the demsg output too.

Regards
Mark


View attachment "dmesg.txt" of type "text/plain" (102499 bytes)