public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vik Heyndrickx" <vik.heyndrickx@pandora.be>
To: <rhw@memalpha.cx>, <linux-kernel@vger.kernel.org>
Cc: <rgooch@atnf.csiro.au>
Subject: 2.4 kernel hangs on 486 machine at boot
Date: Wed, 4 Apr 2001 16:53:54 +0200	[thread overview]
Message-ID: <000701c0bd17$1232f200$04a8a8c0@vortex.prv> (raw)

Hello,

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>

I experience this problem on a VLB AMD 486 DX/2-66 system. This machine ran
all kernels up to 2.2.18 without any problem (it still does).

This 2.4 kernel runs fine on a Pentium, Pentium II and even on a _386DX_
(!!!), but not on my 486 machine (which I am using as a router, and I
thought: let's try the netfilter/iptables feature :) on it).

I tried both the precompiled 2.4 kernels from the Redhat linux releases and
betas, and a couple of self-compiled stock kernels (2.4.0 and 2.4.2) from
ftp://ftp.kernel.org/

Anyway I find it obvious that the kernel hangs only on 486's (and probably
not all of them), so it must be a bug (can I call this an oops? ;-))
I'm not familiar enough with the kernel and protected mode x86 asm to
correct this problem myself, but if anyone would know what may be causing
this (probably in arch/i386/mm/init.c) I can rebuild, install and test any
supplied patches (don't send entire precompiled kernels to me, please).

BTW Keep in mind that I'm not on any kernel related mailing list, but I like
to be informed.

Thanks & kind regards,

--
Vik



             reply	other threads:[~2001-04-04 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04 14:53 Vik Heyndrickx [this message]
2001-04-04 17:54 ` 2.4 kernel hangs on 486 machine at boot Alan Cox
2001-04-04 17:44   ` Vik Heyndrickx
2001-04-04 18:17   ` Brian Gerst
2001-04-05 10:24     ` Pavel Machek
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='000701c0bd17$1232f200$04a8a8c0@vortex.prv' \
    --to=vik.heyndrickx@pandora.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@atnf.csiro.au \
    --cc=rhw@memalpha.cx \
    /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