public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Robert Kaiser <rob@sysgo.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Anybody got 2.4.0 running on a 386 ?
Date: Wed, 10 Jan 2001 13:04:01 -0800	[thread overview]
Message-ID: <3A5CCE41.9050109@megapathdsl.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0101101618120.19662-100000@dagobert.svc.sysgo.de>

Robert Kaiser wrote:

<snip>

>> I have periodically built kernels that crashed
>> immediately at the point you mention.  Usually this
>> was due to me choose configuration options that
>> were incompatible with my machine's hardware.
> 
> 
> You mean they crashed at the exact same statement ?
> That would be an interesting hint, can you confirm it ?

I sent the "possible config problem" list mostly
as a warning about what can cause kernels to lock up
early in the boot cycle.  Some of the problems I ]
mentioned will cause a lock up immediately after
the "Uncompressing kernel... OK Booting Linux" message.

I doubt that these problems are causing your problem
and so I really doubt that these crashes are occuring
in the same function that yours is.

Mostly, I thought you might want to double-check your
configuration options and make sure that you are using
none of these broken configuration combinations.

Good luck!  I wish I could be of more help.

	Miles


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-10 21:05 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 20:53 Anybody got 2.4.0 running on a 386 ? Robert Kaiser
2001-01-09 21:15 ` Brian Gerst
2001-01-09 21:17   ` Robert Kaiser
2001-01-09 21:46     ` Brian Gerst
2001-01-09 22:17       ` Robert Kaiser
2001-01-09 22:57         ` Ingo Molnar
2001-01-09 23:44           ` Robert Kaiser
2001-01-10  0:19             ` Alex Buell
2001-01-10  0:20             ` Ingo Molnar
2001-01-10  0:24               ` Ingo Molnar
2001-01-10 16:00               ` Robert Kaiser
2001-01-10 21:29                 ` Tom G. Christensen
2001-01-10 22:04                   ` X performance on 2.4.0 v.s. 2.4.0-test12 Alan Olsen
2001-01-09 23:03         ` Anybody got 2.4.0 running on a 386 ? Brian Gerst
2001-01-09 23:04           ` Robert Kaiser
2001-01-09 23:28             ` Anuradha Ratnaweera
2001-01-09 23:42               ` Robert Kaiser
2001-01-10  1:48                 ` Miles Lane
2001-01-10 15:25                   ` Robert Kaiser
2001-01-10 21:04                     ` Miles Lane [this message]
2001-01-10 16:28             ` Paul Gortmaker
2001-01-15 18:38               ` [SOLVED + PATCH] " Robert Kaiser
2001-01-15 19:11                 ` Linus Torvalds
2001-01-09 22:44       ` Timur Tabi
2001-01-09 21:59     ` Brian Gerst
2001-01-10 19:51     ` mo6
2001-01-10 20:18       ` Brian Gerst
2001-01-10 21:53         ` mo6
2001-01-11 12:20     ` mo6
2001-01-10  3:53 ` Tom Leete
  -- strict thread matches above, loose matches on Subject: below --
2001-01-10  9:25 richardj_moore
2001-01-10 14:19 ` Alan Cox
2001-01-10 15:04   ` Robert Kaiser
2001-01-10 15:49     ` Alan Cox
2001-01-10 16:02       ` Robert Kaiser
     [not found] <Pine.LNX.4.04.10101101000130.27018-100000@hantana.pdn.ac.lk>
2001-01-10 15:37 ` Robert Kaiser
2001-01-10 17:16 Petr Vandrovec

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=3A5CCE41.9050109@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@sysgo.de \
    /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