public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Disconnect <lkml@sigkill.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon runtime problems
Date: Sat, 14 Apr 2001 23:55:31 -0400	[thread overview]
Message-ID: <20010414235531.B13205@sigkill.net> (raw)
In-Reply-To: <E14oRie-000556-00@the-village.bc.nu>
In-Reply-To: <E14oRie-000556-00@the-village.bc.nu>

[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]

> Can the folks who are seeing crashes running athlon optimised kernels all mail
> me
> -	CPU model/stepping
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 4
model name      : AMD Athlon(tm) Processor
stepping        : 2
cpu MHz         : 1202.743

(/proc/cpuinfo attached) 1.2G Tbird

> -	Chipset

Iwill KK266, VIA KT133

> -	Amount of RAM

512M PC133 amd-approved

> -	/proc/mtrr output
reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
reg01: base=0xd0000000 (3328MB), size=  64MB: write-combining, count=1
reg05: base=0xd8000000 (3456MB), size=  64MB: write-combining, count=1

(This is from inside X on a K6 kernel. I can try to save it out from the
K7 kernel if needed.)

> -	compiler used

gcc version 2.95.3 20010219 (prerelease)
debian gcc 2.95.3-5

---
   _.-=<Disconnect>=-._
|     dis@sigkill.net    | And Remember...
\  shawn@healthcite.com  / He who controls Purple controls the Universe..
 PGP Key given on Request  Or at least the Purple parts!

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1 [www.ebb.org/ungeek]
GIT/CC/CM/AT d--(-)@ s+:-- a-->? C++++$ ULBS*++++$ P+>+++ L++++>+++++ 
E--- W+++ N+@ o+>$ K? w--->+++++ O- M V-- PS+() PE Y+@ PGP++() t 5--- 
X-- R tv+@ b++++>$ DI++++ D++(+++) G++ e* h(-)* r++ y++
------END GEEK CODE BLOCK------

[-- Attachment #2: cpuinfo --]
[-- Type: text/plain, Size: 404 bytes --]

processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 6
model		: 4
model name	: AMD Athlon(tm) Processor
stepping	: 2
cpu MHz		: 1202.743
cache size	: 256 KB
fdiv_bug	: no
hlt_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 mmx fxsr syscall mmxext 3dnowext 3dnow
bogomips	: 2398.61


  parent reply	other threads:[~2001-04-15  3:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-14 15:12 Athlon runtime problems Alan Cox
2001-04-14 15:43 ` Tim lawless
2001-04-14 17:47 ` Kurt Roeckx
2001-04-14 20:14 ` Jeff Lightfoot
2001-04-15  3:25 ` Moses Mcknight
2001-04-15  3:55 ` Disconnect [this message]
2001-04-16 23:52 ` Gary White (Network Administrator)
  -- strict thread matches above, loose matches on Subject: below --
2001-04-16  8:17 David Smith
2001-04-17  5:59 Ray Shaw

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=20010414235531.B13205@sigkill.net \
    --to=lkml@sigkill.net \
    --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