From: Andi Kleen <andi@firstfloor.org>
To: jean-francois simon <jfs@themis.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Initrd problem with AMD opteron dual core
Date: Sat, 10 Nov 2007 17:13:56 +0100 [thread overview]
Message-ID: <p73ir4a13jv.fsf@bingen.suse.de> (raw)
In-Reply-To: <4731630B.2050007@themis.com> (jean-francois simon's message of "Wed\, 07 Nov 2007 08\:02\:35 +0100")
jean-francois simon <jfs@themis.com> writes:
> i don't know where to start to try solving this problem. why would the
> dual core CPUs cause a problem? i fear that just disabling the initrd
> could just mask a more serious problem.
Most likely.
> also i don't understand why /proc/meminfo only reports 1GB...
I would compare the e820 maps between single and dual core. Perhaps the
initrd happens to be loaded somewhere where it overwrite other memory.
Another reason could be broken MTRRs not covering all memory correctly.
This can cause strange mmeory corruptions
Also if single core is an old stepping memory remapping might work
differently.
-Andi
prev parent reply other threads:[~2007-11-10 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 7:02 Initrd problem with AMD opteron dual core jean-francois simon
2007-11-10 16:13 ` Andi Kleen [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=p73ir4a13jv.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=jfs@themis.com \
--cc=linux-kernel@vger.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