From: Mark Hounschell <markh@compro.net>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: Mark Hounschell <dmarkh@cfl.rr.com>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
john stultz <johnstul@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: PROBLEM: Can't boot a (HZ = 1000) kernel using an AMD Phenom-II processor
Date: Tue, 03 Feb 2009 14:15:13 -0500 [thread overview]
Message-ID: <498897C1.2090802@compro.net> (raw)
In-Reply-To: <20090203151137.GB12017@aftab>
Borislav Petkov wrote:
> Hi,
>
> On Tue, Feb 03, 2009 at 04:17:55AM -0500, Mark Hounschell wrote:
>> 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
>
> looks good at a glance...
>
>>> 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.
>
> That's not cool - as I said before, I can't reproduce this behavior here
> which means that the problem might be chipset-related. What you could do
> now is to boot the kernel with "debug initcall_debug log_buf_len=10M"
> and try to capture the whole boot log with a serial console - or if that
> doesn't work - make a screenshot with a camera of some sort. This might
> shed some light on the question where exactly your machine hangs.
>
It will be easier to capture the process on video then rip it out into a
bunch jpegs than it will be to connect the serial port. It's internal and I
don't have the adapter to bring it out the back of the case. I'll see what
I can do. It might be a couple of days but I'll get back to ya.
Thanks
Mark
next prev parent reply other threads:[~2009-02-03 19:15 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
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 [this message]
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=498897C1.2090802@compro.net \
--to=markh@compro.net \
--cc=andreas.herrmann3@amd.com \
--cc=borislav.petkov@amd.com \
--cc=dmarkh@cfl.rr.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).