From: Robert Kaiser <rob@sysgo.de>
To: <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Anybody got 2.4.0 running on a 386 ?
Date: Wed, 10 Jan 2001 00:44:03 +0100 [thread overview]
Message-ID: <01011001040704.03050@rob> (raw)
In-Reply-To: <Pine.LNX.4.30.0101092354140.9990-100000@e2>
In-Reply-To: <Pine.LNX.4.30.0101092354140.9990-100000@e2>
On Die, 09 Jan 2001 you wrote:
> 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).
Sorry, no ext2fs in this kernel (it is for a diskless embedded system). I seem
to recall though that the problem at one point magically went away when I
disabled the FPU emulation, but I have not been able to reproduce this
recently, so I'm not sure. Making minor changes to the kernel code (such as
adding/removing some test-prints) certainly does not affect the behavior.
> Or if that part is not mapped
> correctly (which does happen sometimes as well).
What could I do to check/fix this ?
>
> and are you sure it crashes there? [are you putting delays between your
> printouts?]
I have put a "halting statement" (i.e. "while(1);") after my printouts to make
sure execution does not go any further than that point. I moved this halting
statement ahead in the code line by line until the crash would occur again.
So, yes, I am pretty sure.
>
> > 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).
According to my System.map file, mem_map is at 0xc0244f78. Does that help ?
----------------------------------------------------------------
Robert Kaiser email: rkaiser@sysgo.de
SYSGO RTS GmbH
Am Pfaffenstein 14 phone: (49) 6136 9948-762
D-55270 Klein-Winternheim / Germany fax: (49) 6136 9948-10
-
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/
next prev parent reply other threads:[~2001-01-10 0: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 [this message]
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
-- 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=01011001040704.03050@rob \
--to=rob@sysgo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.