* memtest86 on the opteron
@ 2003-06-07 20:27 dan carpenter
2003-06-07 21:43 ` Pavel Machek
0 siblings, 1 reply; 11+ messages in thread
From: dan carpenter @ 2003-06-07 20:27 UTC (permalink / raw)
To: chris; +Cc: linux-kernel
Is there anyone working on Memtest86 for the AMD Opteron?
What would be involved with making that work?
regards,
dan carpenter
--
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: memtest86 on the opteron
2003-06-07 20:27 memtest86 on the opteron dan carpenter
@ 2003-06-07 21:43 ` Pavel Machek
2003-06-08 2:52 ` Bryan O'Sullivan
0 siblings, 1 reply; 11+ messages in thread
From: Pavel Machek @ 2003-06-07 21:43 UTC (permalink / raw)
To: dan carpenter; +Cc: chris, linux-kernel
Hi!
> Is there anyone working on Memtest86 for the AMD Opteron?
Well, as opteron is i386-compatible, you should be able to simply use
i386 memtest... Should be easy for <2GB memory. You can teach memtest
PAE, that will be usefull to 32GB pentium boxes, too ;-).
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: memtest86 on the opteron
2003-06-07 21:43 ` Pavel Machek
@ 2003-06-08 2:52 ` Bryan O'Sullivan
2003-06-08 8:06 ` Pavel Machek
0 siblings, 1 reply; 11+ messages in thread
From: Bryan O'Sullivan @ 2003-06-08 2:52 UTC (permalink / raw)
To: Pavel Machek; +Cc: dan carpenter, chris, linux-kernel
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.
<b
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: memtest86 on the opteron
2003-06-08 2:52 ` Bryan O'Sullivan
@ 2003-06-08 8:06 ` Pavel Machek
0 siblings, 0 replies; 11+ messages in thread
From: Pavel Machek @ 2003-06-08 8:06 UTC (permalink / raw)
To: Bryan O'Sullivan; +Cc: Pavel Machek, dan carpenter, chris, linux-kernel
Hi!
> > 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.
Try asking AMD at discuss@x86-64.org.
BTW I'm sure I've seen x86_64 machine running some kind of
memtest.... There was mem-testing PCI card. I'm not sure if we ran
memtest86, too...
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <20030607202725.22992.qmail@email.com.suse.lists.linux.kernel>]
* Re: memtest86 on the opteron
@ 2003-06-09 20:26 Dan Carpenter
2003-06-09 21:18 ` Dave Jones
0 siblings, 1 reply; 11+ messages in thread
From: Dan Carpenter @ 2003-06-09 20:26 UTC (permalink / raw)
To: linux-kernel; +Cc: ppokorny
Thanks all,
Here is the patch for the CPU ID.
regards,
dan carpenter
Penguin Computing
--- init.c.orig Mon Jun 9 10:23:10 2003
+++ init.c Mon Jun 9 10:25:44 2003
@@ -402,6 +402,16 @@
}
l1_cache = cpu_id.cache_info[3];
l1_cache += cpu_id.cache_info[7];
+ case 15:
+ switch(cpu_id.model) {
+ case 5:
+ cprint(LINE_CPU, 0, "AMD Opteron");
+ off = 11;
+ l1_cache = cpu_id.cache_info[3];
+ l1_cache += cpu_id.cache_info[7];
+ l2_cache = (cpu_id.cache_info[11] << 8);
+ l2_cache += cpu_id.cache_info[10];
+ }
}
break;
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: memtest86 on the opteron
2003-06-09 20:26 Dan Carpenter
@ 2003-06-09 21:18 ` Dave Jones
2003-06-09 21:29 ` Bryan O'Sullivan
0 siblings, 1 reply; 11+ messages in thread
From: Dave Jones @ 2003-06-09 21:18 UTC (permalink / raw)
To: Dan Carpenter; +Cc: linux-kernel, ppokorny
On Mon, Jun 09, 2003 at 01:26:37PM -0700, Dan Carpenter wrote:
> --- init.c.orig Mon Jun 9 10:23:10 2003
> +++ init.c Mon Jun 9 10:25:44 2003
> @@ -402,6 +402,16 @@
> }
> l1_cache = cpu_id.cache_info[3];
> l1_cache += cpu_id.cache_info[7];
> + case 15:
> + switch(cpu_id.model) {
> + case 5:
> + cprint(LINE_CPU, 0, "AMD Opteron");
> + off = 11;
> + l1_cache = cpu_id.cache_info[3];
> + l1_cache += cpu_id.cache_info[7];
> + l2_cache = (cpu_id.cache_info[11] << 8);
> + l2_cache += cpu_id.cache_info[10];
> + }
> }
Any reason to restrict it to a single stepping ?
This means you have to upgrade memtest every time a new model
is released, which seems a bit of a pain.
Chances are it'll work fine on subsequent family 15 AMD CPUs.
Dave
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: memtest86 on the opteron
2003-06-09 21:18 ` Dave Jones
@ 2003-06-09 21:29 ` Bryan O'Sullivan
2003-06-11 15:51 ` Dan Carpenter
0 siblings, 1 reply; 11+ messages in thread
From: Bryan O'Sullivan @ 2003-06-09 21:29 UTC (permalink / raw)
To: Dave Jones; +Cc: Dan Carpenter, linux-kernel, ppokorny
[-- Attachment #1: Type: text/plain, Size: 377 bytes --]
On Mon, 2003-06-09 at 14:18, Dave Jones wrote:
> Any reason to restrict it to a single stepping ?
> This means you have to upgrade memtest every time a new model
> is released, which seems a bit of a pain.
This is the patch I use, which seems to make sense, since I don't know
of any other steppings. No point in parameterising the code until you
have some parameters.
<b
[-- Attachment #2: memtest.patch --]
[-- Type: text/plain, Size: 732 bytes --]
===== init.c 1.2 vs edited =====
--- 1.2/init.c Mon Jun 9 14:25:40 2003
+++ edited/init.c Mon Jun 9 14:27:42 2003
@@ -403,16 +403,12 @@
l1_cache = cpu_id.cache_info[3];
l1_cache += cpu_id.cache_info[7];
case 15:
- switch (cpu_id.model) {
- case 5:
- cprint(LINE_CPU, 0, "AMD Opteron");
- off = 11;
- l1_cache = cpu_id.cache_info[3];
- l1_cache += cpu_id.cache_info[7];
- l2_cache = (cpu_id.cache_info[11] << 8);
- l2_cache += cpu_id.cache_info[10];
- break;
- }
+ cprint(LINE_CPU, 0, "AMD Opteron");
+ off = 11;
+ l1_cache = cpu_id.cache_info[3];
+ l1_cache += cpu_id.cache_info[7];
+ l2_cache = (cpu_id.cache_info[11] << 8);
+ l2_cache += cpu_id.cache_info[10];
}
break;
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: memtest86 on the opteron
2003-06-09 21:29 ` Bryan O'Sullivan
@ 2003-06-11 15:51 ` Dan Carpenter
0 siblings, 0 replies; 11+ messages in thread
From: Dan Carpenter @ 2003-06-11 15:51 UTC (permalink / raw)
To: Bryan O'Sullivan; +Cc: Dave Jones, linux-kernel, ppokorny
On 9 Jun 2003, Bryan O'Sullivan wrote:
> On Mon, 2003-06-09 at 14:18, Dave Jones wrote:
>
> > Any reason to restrict it to a single stepping ?
> > This means you have to upgrade memtest every time a new model
> > is released, which seems a bit of a pain.
>
> This is the patch I use, which seems to make sense, since I don't know
> of any other steppings. No point in parameterising the code until you
> have some parameters.
>
Grand. I threw in a break statement so it handles Athlons again.
Here is the patch against the original memtest for the mail archives.
thanks,
dan carpenter
Penguin Computing
--- init.c.orig Wed Jun 11 08:49:02 2003
+++ init.c Wed Jun 11 08:43:39 2003
@@ -402,6 +402,14 @@
}
l1_cache = cpu_id.cache_info[3];
l1_cache += cpu_id.cache_info[7];
+ break;
+ case 15:
+ cprint(LINE_CPU, 0, "AMD Opteron");
+ off = 11;
+ l1_cache = cpu_id.cache_info[3];
+ l1_cache += cpu_id.cache_info[7];
+ l2_cache = (cpu_id.cache_info[11] << 8);
+ l2_cache += cpu_id.cache_info[10];
}
break;
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2003-06-11 16:10 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-07 20:27 memtest86 on the opteron dan carpenter
2003-06-07 21:43 ` Pavel Machek
2003-06-08 2:52 ` Bryan O'Sullivan
2003-06-08 8:06 ` Pavel Machek
[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 ` Andi Kleen
2003-06-08 6:44 ` Warren Togami
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).