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

Mark Hounschell
2009-02-03T09:18:13Z

Borislav Petkov wrote:
> On Sat, Jan 31, 2009 at 04:15:58AM -0500, Mark Hounschell wrote:
>
> [..]
>
>> So were you able to reproduce this with my .config. Has anyone booted a Hz=1000
>> kernel on an AMD Phenom-II? Is there something wrong with my .config? Is there
>> anything else I can do?
>
> Hi,
>
> sorry for the delay - I've been busy last week and couldn't get to your
> problem. So, I couldn't reproduce the bug here with a Phenom II and your
> kernel config. However, we have a working theory, so can you please send
> me the output of
>
> xxd /sys/firmware/acpi/tables/APIC
>

markh@harley:~> xxd /sys/firmware/acpi/tables/APIC
0000000: 4150 4943 8400 0000 014c 5258 3738 3020 APIC.....LRX780
0000010: 4157 5244 4143 5049 312e 3042 4157 5244 AWRDACPI1.0BAWRD
0000020: 0000 0000 0000 e0fe 0100 0000 0008 0000 ................
0000030: 0100 0000 0008 0101 0100 0000 0008 0202 ................
0000040: 0100 0000 0008 0303 0100 0000 010c 0400 ................
0000050: 0000 c0fe 0000 0000 020a 0000 0200 0000 ................
0000060: 0000 020a 0009 0900 0000 0f00 0406 0005 ................
0000070: 0001 0406 0105 0001 0406 0205 0001 0406 ................
0000080: 0305 0001

>
> Also, can you boot a 64-bit, HZ1000 kernel on your machine?
>

No, a 64 bit kernel @1000Hz doesn't boot either. As with the 32 bit kernel,
setting Hz to 250 allows it to boot. The messages are slightly different when it
hangs on the 64bit kernel at 1000Hz.

Initializing CPU#0
PID hash table entries: 4096(order: 12,32768 bytes)
TSC calibrated against PM_TIMER
time.c Detected 3000.226 Mhz processor
Console: colour VGA+ 80x25
console [tty0] enabled
Checking aperture...
Node 0: aperture @4000000 size=32MB
Aperture pointing to e820 RAM, Ignoring.
No AGP bridge found
Your BIOS doesn't leave a aperture memory hole
Please enable the IOMMU option in the BIOS setup
This costs you 64MB of RAM
Mapping aperture over 65536 of RAM @4000000
PM: Registered nosave memory: 0000000004000000-0000000008000000
Memory: 4053644k/5242880k available (2355k kernel code, 140144k reserved, 1400k
data, 472 init)

Regards
Mark