public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gordon Sadler <gbsadler1@lcisp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.5pre1 will not boot
Date: Fri, 4 May 2001 21:55:35 -0500	[thread overview]
Message-ID: <20010504215535.A25868@debian-home.lcisp.com> (raw)
In-Reply-To: <3AF26827.11B2A4A9@home.com>

On Fri, May 04, 2001 at 01:28:23AM -0700, Seth Goldberg wrote:Seth Goldberg <bergsoft@home.com>
> Gordon Sadler wrote:
> > 
> > On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote:
> > > Hi,
> Hi,
> 
>  Have you tried compiling ther kernel with Athlon optimiztions turned
> off (try
> compiling for a K6-II[I])?  The has stopped the same thing from
> happening on
> my system and those of a few other people.
> 
I've seen some others reporting some success with K6-II[I] or
Pentium-II[I] configurations. I haven't tried it here as 2.2.19 is
running fine for me. -) I just keep trying the new 2.4.x and reporting
here with hopes someone will find the problem and be able to resolve it.
There could very well be something wrong with my/our hardware. I'm at a
loss as to why none of the developers can reproduce this? Is it possible
none of the 'core' developers have/have access to this hardware? It
isn't all that unusual I think.

If anyone needs more info, just ask. Lots of time/hardrive space here
available for experimenting. (As long as you don't blow it up -) ).

Gordon Sadler



  reply	other threads:[~2001-05-05  2:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-04  7:12 PROBLEM: 2.4.5pre1 will not boot Gordon Sadler
2001-05-04  7:43 ` Seth Goldberg
2001-05-04  8:01   ` Gordon Sadler
2001-05-04  8:28     ` Seth Goldberg
2001-05-05  2:55       ` Gordon Sadler [this message]
2001-05-05  3:05         ` Seth Goldberg

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=20010504215535.A25868@debian-home.lcisp.com \
    --to=gbsadler1@lcisp.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