public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Warren Togami <warren@togami.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: memtest86 on the opteron
Date: 09 Jun 2003 10:04:16 -0600	[thread overview]
Message-ID: <m17k7v1blr.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1055054691.18692.13.camel@laptop>

Warren Togami <warren@togami.com> writes:

> 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?

memtest86 has PAE support so it should be able to test everything.
I have tested with 6GB of RAM on an old PIII.

Beyond the cpuid thing.  There is a bug in the probing of how much memory
is cached.  Last time I was playing with it I just disabled that section
of code.

If nothing else ping me a few times because I will need this shortly.
If it really does not work.  And I am familiar with the code so I will
certainly get it fixed.

Eric

  reply	other threads:[~2003-06-09 15:51 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
2003-06-09 16:04         ` Eric W. Biederman [this message]
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=m17k7v1blr.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=warren@togami.com \
    /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