public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Vik Heyndrickx <vik.heyndrickx@pandora.be>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4 kernel hangs on 486 machine at boot
Date: Thu, 5 Apr 2001 10:24:55 +0000	[thread overview]
Message-ID: <20010405102454.A31@(none)> (raw)
In-Reply-To: <E14krU0-0002P8-00@the-village.bc.nu> <3ACB6524.C5986233@didntduck.org>
In-Reply-To: <3ACB6524.C5986233@didntduck.org>; from bgerst@didntduck.org on Wed, Apr 04, 2001 at 02:17:08PM -0400

Hi!

> > > Problem: Linux kernel 2.4 consistently hangs at boot on 486 machine
> > >
> > > Shortly after lilo starts the kernel it hangs at the following message:
> > > Checking if this processor honours the WP bit even in supervisor mode...
> > > <blinking cursor>
> > 
> > Does this happen on 2.4.3-ac kernel trees ? I thought i had it zapped
> 
> Yes, that fix in -ac should take care of it.  As to why only the 486
> showed the problem, most 386's will not fault on the write protected
> page (the whole reason for this test) and pentiums and later don't run
> the test at all (assumed good).

We should not "assume good" -- to catch bugs like this one.
-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  reply	other threads:[~2001-04-07 18:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04 14:53 2.4 kernel hangs on 486 machine at boot Vik Heyndrickx
2001-04-04 17:54 ` Alan Cox
2001-04-04 17:44   ` Vik Heyndrickx
2001-04-04 18:17   ` Brian Gerst
2001-04-05 10:24     ` Pavel Machek [this message]
2001-04-07 18:15       ` Brian Gerst

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='20010405102454.A31@(none)' \
    --to=pavel@suse.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bgerst@didntduck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vik.heyndrickx@pandora.be \
    /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