public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: Carl-Johan Kjellander <carljohan@kjellander.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 386 boot problems with 2.4.7 and 2.4.7-ac9
Date: Wed, 08 Aug 2001 19:23:43 -0400	[thread overview]
Message-ID: <3B71C9FF.B2E0979C@didntduck.org> (raw)
In-Reply-To: <3B706C11.7010100@kjellander.com>

Carl-Johan Kjellander wrote:
> 
> I have an old 386 which ran 2.4.3 just fine. Last night i tried
> to upgrade it but it didnt work at all.
> 
> I compiled a stock 2.4.7, and since I had seen some postings on
> that egcs-2.91.66 didn't compile 2.4.7 I switched to gcc-2.96-85.
> The only thing I added to the kernel was ISAPNP support.
> 
> The 2.4.7 kernel seems to boot fine, no error messages or nothing,
> but it won't start init. The last line is:
> 
>    Freeing unused kernel memory: 52K freed
> 
> And then it just stops. The kernel is still resonsive but init won't
> start. Shift-PageUp still works. SysRQ shows that the EIP almost
> always is on the same spot in schedule. I tried init=/bin/sh but
> the boot stops at the same place every time.
> 
> Then I tried 2.4.7-ac9, same configuration, but that kernel panics.

Are you using math emulation?  If so there was a bug fixed in the
2.4.8-pre kernels.

--
						Brian Gerst

  parent reply	other threads:[~2001-08-08 23:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 22:30 386 boot problems with 2.4.7 and 2.4.7-ac9 Carl-Johan Kjellander
2001-08-07 22:47 ` Carl-Johan Kjellander
2001-08-08 23:23 ` Brian Gerst [this message]
2001-08-09 10:31 ` Maciej Zenczykowski
2001-08-08 12:05   ` Carl-Johan Kjellander
     [not found] ` <3B7419B5.1C029DF4@osdlab.org>
2001-08-10  2:47   ` Carl-Johan Kjellander
     [not found] <no.id>
2001-08-08 23:02 ` 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=3B71C9FF.B2E0979C@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=carljohan@kjellander.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