From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: aowi@novozymes.com,
Andreas Herrmann <herrmann.der.user@googlemail.com>,
"JK (Jesper Agerbo Krogh)" <JK@novozymes.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Tejun Heo <tj@kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: Memory issues with Opteron 6220
Date: Sat, 11 Feb 2012 14:50:20 +0100 [thread overview]
Message-ID: <20120211135019.GE28098@elte.hu> (raw)
In-Reply-To: <CAE9FiQUc5Xzvt94sS5HBmQ9E1hyB7GRozP2-xgZk=9y4AUOk9g@mail.gmail.com>
* Yinghai Lu <yinghai@kernel.org> wrote:
> On Thu, Feb 9, 2012 at 9:51 AM, Anders Ossowicki <aowi@novozymes.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.
Mind sending a patch that puts it back, so that it's printed via
KERN_DEBUG or such, i.e. does not get emitted in the default
log. Maybe even tie it to apic=debug or so.
Thanks,
Ingo
prev parent reply other threads:[~2012-02-11 13:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 14:37 Anders Ossowicki
2012-02-09 8:33 ` Ingo Molnar
2012-02-09 9:08 ` Eric Dumazet
2012-02-09 13:23 ` Ingo Molnar
2012-02-09 21:07 ` Jesper Krogh
2012-02-10 15:21 ` Jesper Krogh
2012-02-11 13:48 ` Ingo Molnar
2012-02-14 9:32 ` Anders Ossowicki
[not found] ` <20120208205628.GA18909@alberich.amd.com>
2012-02-09 12:43 ` Anders Ossowicki
2012-02-09 13:28 ` Ingo Molnar
2012-02-09 13:49 ` Anders Ossowicki
2012-02-09 16:11 ` Yinghai Lu
2012-02-09 17:51 ` Anders Ossowicki
2012-02-09 18:56 ` Yinghai Lu
2012-02-11 13:50 ` Ingo Molnar [this message]
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=20120211135019.GE28098@elte.hu \
--to=mingo@elte.hu \
--cc=JK@novozymes.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=aowi@novozymes.com \
--cc=eric.dumazet@gmail.com \
--cc=herrmann.der.user@googlemail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=yinghai@kernel.org \
/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
Powered by JetHome