mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Chan <cshihpin@dso.org.sg>
To: linux-kernel@vger.kernel.org
Cc: arjanv@redhat.com
Subject: Athlon oops traced to CONFIG_MK7 code in arch/i386/lib/mmx.c
Date: Sat, 7 Jul 2001 09:10:46 -0800	[thread overview]
Message-ID: <20010707091046.A2355@cshihpin.dso.org.sg> (raw)

Athlon oops saga continues - I consistently get Athlon kernels oopsing
during the boot up process either in rc.sysinit or loading of usb modules
(this is a RedHat system 7.1). These kernels can boot to a shell init=/bin/sh
but once I try to do stuff like inserting modules they oops left, right, and centre.

System: Athlon 1.2GHz VIA KT 133A
Kernel: 2.4.5 and -ac, 2.4.6 and -ac
Compiler: gcc 2.96-RH/3.00/3.01 binutils 2.10.90/2.11.2/2.11.90


I have narrowed a(the?) problem down to the CONFIG_MK7 specific code in arch/i386/lib/mmx.c.
If I disable CONFIG_MK7 in that one file with the rest of the kernel untouched and
compiled with CONFIG_MK7 and -march=athlon then my kernel boots sucessfully and manages
to get into multi-user mode. With a few minutes of testing and X everything works fine.

I'm interested if there is an explanation of the MK7 specific code in mmx.c and
whether that could really be the source of the problem. I would like to get
to the bottom of this.

FWIW - the RedHat 7.1 stock 2.4.2 athlon kernel boots successfully without oopsen.

Thanks!

Richard Chan <cshihpin@dso.org.sg>

             reply	other threads:[~2001-07-07  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-07 17:10 Richard Chan [this message]
2001-07-07  8:27 ` Arjan van de Ven
2001-07-07 12:19 ` 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=20010707091046.A2355@cshihpin.dso.org.sg \
    --to=cshihpin@dso.org.sg \
    --cc=arjanv@redhat.com \
    --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

all inboxes | Powered by JetHome®