[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQUc5Xzvt94sS5HBmQ9E1hyB7GRozP2-xgZk=9y4AUOk9g@mail.gmail.com>
Date: Thu, 9 Feb 2012 10:56:44 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: aowi@...ozymes.com, Yinghai Lu <yinghai@...nel.org>,
Ingo Molnar <mingo@...e.hu>,
Andreas Herrmann <herrmann.der.user@...glemail.com>,
"JK (Jesper Agerbo Krogh)" <JK@...ozymes.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, Tejun Heo <tj@...nel.org>,
Eric Dumazet <eric.dumazet@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: Memory issues with Opteron 6220
On Thu, Feb 9, 2012 at 9:51 AM, Anders Ossowicki <aowi@...ozymes.com> wrote:
> On Thu, Feb 09, 2012 at 05:11:04PM +0100, Yinghai Lu wrote:
>> mtrr setting has some problem too.
>>
>> [ 3.098277] mtrr: your CPUs had inconsistent fixed MTRR settings
>> [ 3.100001] mtrr: probably your BIOS does not setup all CPUs.
>> [ 3.110000] mtrr: corrected configuration.
>>
>> can you boot with "debug ignore_loglevel show_msr=16" ?
>
> Yep, right here:
> http://dev.exherbo.org/~arkanoid/atlas-dmesg-3.2.5-20120209-mtrr.txt
>
Too bad, print_cpu_info() calling for AP get removed by some commit.
now we can not print initial AP register anymore.
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists