public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: PEIFFER Pierre <ppeiffer@free.fr>
To: linux-kernel@vger.kernel.org
Subject: VIA KT133A / athlon / MMX
Date: Fri, 27 Jul 2001 21:42:06 -0400	[thread overview]
Message-ID: <3B62186E.B89C29E8@free.fr> (raw)

Hi !

	I'm a recent user of the duo VIA KT133A chipset/Athlon CPU and after
compiling a customized kernel and booting on it, I fall on kernel panic
at boot time, just little time after starting the init process.
	After some search and test, it appears that it was the K7 mmx routines
which cause the crash
	Using the "default" routines by replacing #ifdef CONFIG_MK7 by #ifdef 0
solves the problem.
	I just wanted to mention that, here, this crash is systematic with
k7-mmx routines.

	I also just wanted to know the current status of this problem since I
have not found clear answer on the different threads about this topic.
As I understand, this problem does not exist on every athlon but only on
some which work with the VIA KT133 chipset ? Right ?
	
	Anyway, feel free to ask me more information if needed and please,
CC'ed me personally the answers/comments because I'm not subscribed to
the LKML.

Config.:
ABIT KT7A (without RAID)
Athlon 1.2 GHz
256 Meg RAM
FSB at 133 MHz
(Other card description is not imortant I think)
Running Mandrake 8.0 (*) (at home)
with kernel 2.4.7 (or 2.4.6) compiled with gcc 3.0 (same pb with gcc
2.96 (non-official, I know))

(*) In fact, this distribution has a special startup and switch
immediatly (at startup) in a graphic mode for showing the start of the
runlevel. And I think/suppose that this definitly causes the crash.

	Thanks,

	Pierre

             reply	other threads:[~2001-07-27 19:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-28  1:42 PEIFFER Pierre [this message]
2001-07-30 21:33 ` VIA KT133A / athlon / MMX Stefan Becker
     [not found] <no.id>
2001-07-27 20:19 ` Alan Cox
2001-07-27 20:37   ` Chris Wedgwood
2001-07-27 20:40     ` Alan Cox
     [not found]       ` <3B61E5BC.5780E1E@randomlogic.com>
2001-07-27 22:12         ` Paul G. Allen
2001-07-28  0:04       ` Kurt Garloff
2001-07-28  0:23       ` David Lang
2001-07-28 11:11         ` Kurt Garloff
2001-07-28 11:49           ` Victor Julien
2001-07-29  0:37           ` J. Dow
2001-07-28 12:47         ` Alan Cox
2001-07-31 19:53           ` David Lang
2001-07-29  4:03       ` Gav
2001-07-29 16:10         ` Mike Frisch
2001-07-30  7:15         ` Steffen Persvold
2001-07-30 10:17           ` Maciej Zenczykowski
2001-07-30 14:35             ` Luigi Genoni
2001-07-30 13:59           ` Gav
2001-07-28 17:29     ` PEIFFER Pierre
2001-07-28 12:21       ` Kurt Garloff
2001-07-28 22:00         ` PEIFFER Pierre
2001-07-29 20:28           ` Kurt Garloff
2001-07-30  6:04             ` Daniela Engert
2001-07-30 13:44               ` Kurt Garloff
2001-07-30 14:15                 ` Michael
2001-07-30 15:46                   ` Kurt Garloff
2001-07-30 18:43                     ` Kurt Garloff
2001-07-30 20:44                       ` Gerbrand van der Zouw
2001-07-30 16:47                 ` Daniela Engert

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=3B62186E.B89C29E8@free.fr \
    --to=ppeiffer@free.fr \
    --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