public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carsten Leonhardt <leo@debian.org>
To: linux-kernel@vger.kernel.org
Subject: Athlon/K7-Opimisation problems
Date: 09 Sep 2001 19:07:39 +0200	[thread overview]
Message-ID: <87g09w70o4.fsf@cymoril.oche.de> (raw)

Hi,

here's my data regarding the K7 optimisation problem.

Until last week I had a 1GHz Athlon with 133MHz FSB. I then bought a
1.4GHz Athlon, again 133MHz FSB.

I never had any problems with the 1GHz processor, but as soon as I
stuck the 1.4GHz processor in, the kernel oopsed itself to
oblivion. (That was with kernel 2.4.5-ac5, approximately)

I also noticed that the computer booted ok with the Debian
bootfloppies, which use a kernel compiled for i386. So after several
kernel compile/boot cycles, I found out that I had to disable K7
optimisation to make the system boot again.

The mainboard is a Tyan Trinity KT-A (S2390B) with a VIA KT133A
chipset.

After reading here that it may be the PSU, I upgraded my 300W PSU to a
431W Enermax, which made no difference.

The only difference I can make out between the working and the
non-working CPU is the internal clockspeed of the CPU and the
stepping (old: 2, new: 4).

Appended is the output of /proc/cpuinfo (I sold the old CPU, but the
guy who bought it sent me the output).

I really hope this helps someone. If anyone needs any more data, or
wants me to test something, contact me.


Yours,
 leo



Old CPU:

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 4
model name      : AMD Athlon(tm) Processor
stepping        : 2
cpu MHz         : 1012.530
cache size      : 256 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 6 mce cx8 sep mtrr pge 14 cmov
pat 17 psn mmxext mmx fxsr 3dnowext 3dnow
bogomips        : 2018.51

New CPU:

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 4
model name      : AMD Athlon(tm) Processor
stepping        : 4
cpu MHz         : 1400.098
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        : 2791.83

             reply	other threads:[~2001-09-09 17:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-09 17:07 Carsten Leonhardt [this message]
2001-09-09 22:11 ` Athlon/K7-Opimisation problems Nicholas Knight
2001-09-09 22:23   ` J. Dow
2001-09-09 22:29     ` Nicholas Knight
2001-09-09 22:49       ` J. Dow
2001-09-09 23:44         ` Nicholas Knight
2001-09-09 23:49       ` Carsten Leonhardt
2001-09-10  6:35         ` J. Dow
2001-09-10  6:56           ` Jan Niehusmann
2001-09-10 15:16           ` Liakakis Kostas
2001-09-10  2:18       ` David Hollister
2001-09-20 20:43   ` bill davidsen
     [not found] <Pine.LNX.4.10.10109211552370.12592-100000@coffee.psychology.mcmaster.ca>
2001-09-23 11:58 ` Bill Davidsen

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=87g09w70o4.fsf@cymoril.oche.de \
    --to=leo@debian.org \
    --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