From: Mark Hounschell <dmarkh@cfl.rr.com>
To: markh@compro.net
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Can't boot a (HZ = 1000) kernel using an AMD Phenom-II processor
Date: Mon, 19 Jan 2009 18:05:12 -0500 [thread overview]
Message-ID: <49750728.8060005@cfl.rr.com> (raw)
In-Reply-To: <49749208.9060807@compro.net>
Mark Hounschell wrote:
> Bartlomiej Zolnierkiewicz wrote:
>> On Monday 19 January 2009, Mark Hounschell wrote:
>>> Mark Hounschell wrote:
>>>> I upgraded from a Phenom to a Phenom-II processor and I could no longer boot.
>>>>
>>>> I have tried kernels from 2.6.26 through 2.6.28.
>>>>
>>>> I _can_ however boot these kernels when they are configured for HZ = 250. I
>>>> haven't tried HZ = 300. But certainly if HZ = 1000 the boot hangs at the spot
>>>> indicated below in the dmesg output.
>>>>
>>>> The machine is up and stable running 2.6.26.8 with a (HZ = 1000) configured kernel.
>>>>
>>> The machine is up and stable running 2.6.26.8 with a (HZ = 250) configured
>>> kernel. Sorry.
>>>
>>>> While running a 2.6.26.8 kernel configured for HZ = 250:
>> [...]
>>
>>>> Checking if this processor honours the WP bit even in supervisor mode...Ok.
>>>>
>>>>
>>>> The 2.6.26.8 kernel hangs up right here.
>>>>
>>>>
>>>> CPA: page pool initialized 1 of 1 pages preallocated
>>>> SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
>>>> hpet clockevent registered
>>>> calibrate_delay_direct() failed to get a good estimate for loops_per_jiffy.
>>>> Probably due to long platform interrupts. Consider using "lpj=" boot option.
>>>> Calibrating delay loop... 3956.73 BogoMIPS (lpj=7913472)
>> Even if it boots it may not work reliably since lpj/BogoMIPS are too small
>> (they should be the same as for other CPUs) which in turn could result in too
>> short delay loops.
>>
>>>> Security Framework initialized
>>>> Capability LSM initialized
>>>> Mount-cache hash table entries: 512
>>>> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
>>>> CPU: L2 Cache: 512K (64 bytes/line)
>>>> CPU 0(4) -> Core 0
>>>> Checking 'hlt' instruction... OK.
>>>> ACPI: Core revision 20080321
>>>> ENABLING IO-APIC IRQs
>>>> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
>>>> CPU0: AMD Processor model unknown stepping 02
>>>> Booting processor 1/1 ip 2000
>>>> Initializing CPU#1
>>>> Calibrating delay using timer specific routine.. 6000.60 BogoMIPS (lpj=12001200)
>> Here are the proper values.
>>
>>>> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
>>>> CPU: L2 Cache: 512K (64 bytes/line)
>>>> CPU 1(4) -> Core 2
>>>> x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
>>>> CPU1: AMD Processor model unknown stepping 02
>>>> Booting processor 2/2 ip 2000
>>>> Initializing CPU#2
>>>> Calibrating delay using timer specific routine.. 6000.47 BogoMIPS (lpj=12000950)
>> also OK
>>
>>>> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
>>>> CPU: L2 Cache: 512K (64 bytes/line)
>>>> CPU 2(4) -> Core 1
>>>> x86 PAT enabled: cpu 2, old 0x7040600070406, new 0x7010600070106
>>>> CPU2: AMD Processor model unknown stepping 02
>>>> Booting processor 3/3 ip 2000
>>>> Initializing CPU#3
>>>> Calibrating delay using timer specific routine.. 6000.47 BogoMIPS (lpj=12000955)
>> ditto
>>
>> That being said I don't know why delay calibration loop fails on CPU0.
>>
>> You may try booting with "lpj=12001200" kernel parameter to workaround
>> the issue (it should fix booting with HZ == 1000) and/or try 2.6.29-rc2
>> (the problem may have been already fixed).
>>
>> Thanks,
>> Bart
>>
>
> I'll try "lpj=12001200" and 2.6.29-rc2 later when I get home this ev.
>
> But I noticed CPU2 is different too. Is CPU1 the correct one?
>
>>>> Initializing CPU#0
>>>> Calibrating delay loop... 3956.73 BogoMIPS (lpj=7913472)
>
>>>> Initializing CPU#1
>>>> Calibrating delay using timer specific routine.. 6000.60 BogoMIPS (lpj=12001200)
>
>>>> Initializing CPU#2
>>>> Calibrating delay using timer specific routine.. 6000.47 BogoMIPS (lpj=12000950)
>
>>>> Initializing CPU#3
>>>> Calibrating delay using timer specific routine.. 6000.47 BogoMIPS (lpj=12000955)
>
None of the lpj values made any difference. 2.6.29-rc2 did print a couple more
messages. The last one was
Using C1E aware idle routine
Checking 'hlt' in
Surely I can't be the only Linux user with this processor???
Regards
Mark
next prev parent reply other threads:[~2009-01-19 23:05 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 12:38 PROBLEM: Can't boot a (HZ = 1000) kernel using an AMD Phenom-II processor Mark Hounschell
2009-01-19 8:48 ` Mark Hounschell
2009-01-19 12:41 ` Bartlomiej Zolnierkiewicz
2009-01-19 14:45 ` Mark Hounschell
2009-01-19 23:05 ` Mark Hounschell [this message]
2009-01-19 14:22 ` Borislav Petkov
2009-01-19 14:54 ` Mark Hounschell
2009-01-19 23:14 ` Mark Hounschell
2009-01-20 0:25 ` john stultz
2009-01-20 9:08 ` Mark Hounschell
2009-01-20 9:37 ` Andreas Herrmann
2009-01-20 21:08 ` Mark Hounschell
2009-01-23 9:34 ` Mark Hounschell
2009-01-23 13:04 ` Andreas Herrmann
2009-01-23 14:47 ` Borislav Petkov
2009-01-23 22:24 ` Mark Hounschell
2009-01-23 22:46 ` Mark Hounschell
2009-01-26 18:26 ` Mark Hounschell
2009-01-27 16:38 ` Borislav Petkov
2009-01-28 0:30 ` Mark Hounschell
2009-01-28 0:33 ` Mark Hounschell
2009-01-31 9:15 ` Mark Hounschell
2009-02-02 17:05 ` Borislav Petkov
2009-02-03 9:17 ` Mark Hounschell
2009-02-03 15:11 ` Borislav Petkov
2009-02-03 19:15 ` Mark Hounschell
2009-02-05 17:19 ` Mark Hounschell
2009-02-06 13:52 ` Borislav Petkov
2009-02-06 14:11 ` Mark Hounschell
2009-02-06 17:55 ` Mark Hounschell
2009-02-06 22:20 ` Mark Hounschell
2009-02-09 14:18 ` Borislav Petkov
2009-02-09 15:29 ` Mark Hounschell
2009-02-18 13:11 ` Mark Hounschell
2009-02-18 14:18 ` Borislav Petkov
2009-02-18 16:57 ` Mark Hounschell
2009-02-18 17:42 ` Borislav Petkov
2009-02-18 21:16 ` Mark Hounschell
2009-02-19 10:37 ` Mark Hounschell
2009-02-19 14:11 ` Andreas Herrmann
2009-02-19 15:16 ` Mark Hounschell
2009-02-19 15:19 ` Borislav Petkov
2009-02-19 15:54 ` Mark Hounschell
2009-02-20 11:53 ` Andreas Herrmann
2009-02-20 12:34 ` Ingo Molnar
2009-02-20 21:51 ` Andreas Herrmann
2009-02-20 15:43 ` Mark Hounschell
2009-02-20 16:08 ` Andreas Herrmann
2009-02-20 16:38 ` Andreas Herrmann
2009-02-20 17:09 ` Mark Hounschell
2009-02-20 17:40 ` Mark Hounschell
2009-02-20 18:22 ` Andreas Herrmann
2009-02-20 18:28 ` Mark Hounschell
2009-02-20 19:54 ` Mark Hounschell
2009-02-20 20:27 ` Mark Hounschell
2009-02-20 22:28 ` Andreas Herrmann
2009-02-21 1:14 ` Mark Hounschell
2009-02-21 13:20 ` Mark Hounschell
2009-02-20 17:06 ` Mark Hounschell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49750728.8060005@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).