From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: Borislav Petkov <borislav.petkov@amd.com>,
Mark Hounschell <markh@compro.net>,
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: Fri, 20 Feb 2009 12:09:14 -0500 [thread overview]
Message-ID: <499EE3BA.7070105@cfl.rr.com> (raw)
In-Reply-To: <20090220163844.GG4834@alberich.amd.com>
Andreas Herrmann wrote:
> On Fri, Feb 20, 2009 at 05:08:43PM +0100, Andreas Herrmann wrote:
>> On Fri, Feb 20, 2009 at 10:43:03AM -0500, Mark Hounschell wrote:
>>> Linux version 2.6.28.3-250Hz (root@harley) (gcc version 4.3.1
>>> 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux)
>>> ) #7 SMP PREEMPT Fri Feb 2 0 09:01:54 EST 2009
>> Here I doubt that's the right kernel -- at least it was not built today.
>> Can you please double check this.
>
> Oops, your kernel was built today.
> Have overlooked it as there was a newline between "2" and "0".
> Sorry for the noise.
>
> But still wondering where's the debug output. I've applied the patch
> both to .29-rc5 and with some fuzziness to .28.4 and on my system the
> output is visible (e.g. with dmesg). Ah, ... of course you need to use
> "debug" kernel parameter as well. Otherwise the KERN_DEBUG messages
> are not shown on the serial console.
>
> Please, can you retry using "hpet=debug debug apic=debug".
> Thanks.
>
>
> Andreas
>
>
>
Ah yes, ok....
It will be forthcoming.
Mark
next prev parent reply other threads:[~2009-02-20 17:09 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
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 [this message]
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=499EE3BA.7070105@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=andreas.herrmann3@amd.com \
--cc=borislav.petkov@amd.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--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).