From: Gordon Sadler <gbsadler1@lcisp.com>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: Info on Athlon/Duron failure as requested
Date: Thu, 3 May 2001 15:03:46 -0500 [thread overview]
Message-ID: <20010503150346.A18141@debian-home.lcisp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 51 bytes --]
See attachment for info requested.
Gordon Sadler
[-- Attachment #2: X988920011-12614-0.gbsadler --]
[-- Type: text/plain, Size: 1300 bytes --]
From: gbsadler1@lcisp.com (Gordon Sadler)
Subject: Re: Athlon runtime problems
In-Reply-To: <linux.kernel.E14oRie-000556-00@the-village.bc.nu>
Reply-To: gbsadler1@lcisp.com
On Sat, 14 Apr 2001 16:12:09 +0100 (BST), Alan Cox
<alan@lxorguk.ukuu.org.uk> wrote:
> Can the folks who are seeing crashes running athlon optimised kernels
> all mail
> me
>
> - CPU model/stepping
$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 3
model name : AMD Duron(tm) Processor
stepping : 1
cpu MHz : 801.828
cache size : 64 KB
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
cmov pat pse36 psn mmxext mmx fxsr 3dnowext 3dnow
bogomips : 1599.07
> - Chipset
VIA KT133A AGPset (KT133A+VT82C686B)
> - Amount of RAM
128 MB
> - /proc/mtrr output
$ cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size= 128MB: write-back, count=1
> - compiler used
$gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20010319 (Debian prerelease)
next reply other threads:[~2001-05-03 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 20:03 Gordon Sadler [this message]
2001-05-04 8:40 ` Idea for Athlon/Duron failure testing Seth Goldberg
2001-05-04 9:54 ` Athlon/VIA Kernel Experimentation (mmx.c) Seth Goldberg
2001-05-04 13:21 ` Brian Gerst
2001-05-04 16:57 ` Seth Goldberg
2001-05-04 14:09 ` Alan Cox
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=20010503150346.A18141@debian-home.lcisp.com \
--to=gbsadler1@lcisp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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