All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Richard Chan <cshihpin@dso.org.sg>
Cc: linux-kernel@vger.kernel.org, arjanv@redhat.com
Subject: Re: Athlon oops traced to CONFIG_MK7 code in arch/i386/lib/mmx.c
Date: Sat, 7 Jul 2001 04:27:15 -0400	[thread overview]
Message-ID: <20010707042715.B6815@devserv.devel.redhat.com> (raw)
In-Reply-To: <20010707091046.A2355@cshihpin.dso.org.sg>
In-Reply-To: <20010707091046.A2355@cshihpin.dso.org.sg>; from cshihpin@dso.org.sg on Sat, Jul 07, 2001 at 09:10:46AM -0800

On Sat, Jul 07, 2001 at 09:10:46AM -0800, Richard Chan wrote:
> 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.
> 
What motherboard, how big is your PSU ?
This code has the tendency to get full memory-bandwidth and it appears that
some boards can't handle this....


Greetings,
   Arjan van de Ven

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-07 17:10 Athlon oops traced to CONFIG_MK7 code in arch/i386/lib/mmx.c Richard Chan
2001-07-07  8:27 ` Arjan van de Ven [this message]
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=20010707042715.B6815@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=cshihpin@dso.org.sg \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.