public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hollister <david@digitalaudioresources.org>
To: tegeran@home.com
Cc: "J. Dow" <jdow@earthlink.net>, Carsten Leonhardt <leo@debian.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Athlon/K7-Opimisation problems
Date: Sun, 09 Sep 2001 19:18:24 -0700	[thread overview]
Message-ID: <3B9C22F0.6030206@digitalaudioresources.org> (raw)
In-Reply-To: <87g09w70o4.fsf@cymoril.oche.de> <01090915115400.00173@c779218-a> <063301c1397e$0efa6d00$1125a8c0@wednesday> <01090915292502.00173@c779218-a>

Nicholas Knight wrote:
> 
> Do most people that experience this problem also experience after a 
> cold-boot where the system had been off for at least 10-15 minutes? And 
> has ANYONE sucsesfully cured this problem by changing power supplies?

I can get it to oops before the rc scripts are done, even from cold boot.  I 
have not swapped power supplies.  I seriously doubt that's the problem.



-- 
David Hollister
Driversoft Engineering:  http://devicedrivers.com
Digital Audio Resources: http://digitalaudioresources.org


  parent reply	other threads:[~2001-09-10  2:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-09 17:07 Athlon/K7-Opimisation problems Carsten Leonhardt
2001-09-09 22:11 ` 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 [this message]
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=3B9C22F0.6030206@digitalaudioresources.org \
    --to=david@digitalaudioresources.org \
    --cc=jdow@earthlink.net \
    --cc=leo@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tegeran@home.com \
    /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