mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Robert Kaiser <rob@sysgo.de>
Cc: Brian Gerst <bgerst@didntduck.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Anybody got 2.4.0 running on a 386 ?
Date: Tue, 9 Jan 2001 23:57:37 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.30.0101092354140.9990-100000@e2> (raw)
In-Reply-To: <01010923324500.02850@rob>


On Tue, 9 Jan 2001, Robert Kaiser wrote:

> Now comes the amazing (to me) part: I split the above statement up into:
>
> 	temp = mk_pte_phys(__pa(vaddr), PAGE_KERNEL);
> 	*pte = temp;

this is almost impossible (except some really weird compiler bug) - unless
the mem_map address is invalid. This could happen if your kernel image is
*just* too large. Do things improve if you disable eg. ext2fs support (i
know, but should be enough to boot). Or if that part is not mapped
correctly (which does happen sometimes as well).

and are you sure it crashes there? [are you putting delays between your
printouts?]

> where temp is declared "volatile pte_t". I inserted test-prints between the
> above two lines. Accoding to that, the _first_ line , i.e. the evaluation of the
> mk_pte_phys() macro is causing the crash!

it accesses mem_map variable, which is near to the end of the kernel
image, so it could indeed something of that sort. An uncompressed kernel
image (including the data area) must not be bigger than 4MB (IIRC).

	Ingo

-
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-09 22:58 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 20:53 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 [this message]
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
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
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=Pine.LNX.4.30.0101092354140.9990-100000@e2 \
    --to=mingo@elte.hu \
    --cc=bgerst@didntduck.org \
    --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

all inboxes | Powered by JetHome®