From: Warren Togami <warren@togami.com>
To: linux-kernel@vger.kernel.org
Subject: Re: memtest86 on the opteron
Date: 07 Jun 2003 20:44:51 -1000 [thread overview]
Message-ID: <1055054691.18692.13.camel@laptop> (raw)
In-Reply-To: <p73of195bj1.fsf@oldwotan.suse.de>
On Sat, 2003-06-07 at 20:27, Andi Kleen wrote:
> Bryan O'Sullivan <bos@serpentine.com> writes:
>
> > On Sat, 2003-06-07 at 14:43, Pavel Machek wrote:
> >
> > > Well, as opteron is i386-compatible, you should be able to simply use
> > > i386 memtest...
> >
> > It doesn't work. Crashes and reboots the system shortly after it
> > starts. The serial console support appears to have bit-rotted, too, so
> > I've not been able to capture an output screen to diagnose the problem.
>
> The problem is the CPUID handling in memtest86. It does not expect
> the 15 model number on AMD systems. Someone did a patch for it, but
> I don't remember where they put it. Anyways should be easy to fix again
> given the source.
>
If you find the patch I am interested in it. Please CC me.
I am guessing that a normal 32bit compiled memtest86 wont be able to
test beyond 4GB of RAM on AMD64?
Warren
next prev parent reply other threads:[~2003-06-08 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030607202725.22992.qmail@email.com.suse.lists.linux.kernel>
[not found] ` <20030607214356.GF667@elf.ucw.cz.suse.lists.linux.kernel>
[not found] ` <1055040745.27939.3.camel@camp4.serpentine.com.suse.lists.linux.kernel>
2003-06-08 6:27 ` memtest86 on the opteron Andi Kleen
2003-06-08 6:44 ` Warren Togami [this message]
2003-06-09 16:04 ` Eric W. Biederman
2003-06-09 20:26 Dan Carpenter
2003-06-09 21:18 ` Dave Jones
2003-06-09 21:29 ` Bryan O'Sullivan
2003-06-11 15:51 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2003-06-07 20:27 dan carpenter
2003-06-07 21:43 ` Pavel Machek
2003-06-08 2:52 ` Bryan O'Sullivan
2003-06-08 8:06 ` Pavel Machek
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=1055054691.18692.13.camel@laptop \
--to=warren@togami.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.