From: Paul Mackerras <paulus@linuxcare.com.au>
To: Tilmann Bitterberg <tibit-ibm@bitterberg.de>
Cc: Linuxppc Development Mailing List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: CONFIG_HIGHMEM problems
Date: Sat, 9 Sep 2000 20:12:48 +1100 (EST) [thread overview]
Message-ID: <14777.65296.649836.830091@argo.linuxcare.com.au> (raw)
In-Reply-To: <Pine.LNX.4.21.0009081006530.1436-200000@ford>
Tilmann Bitterberg writes:
> After looking at arch/ppc/mm/init.c:pmac_find_end_of_memory, I
> realized that there is no chance to return a total of more than
> ram_limit (which is in 512MB in my case).
Hmmm, you're right, the ram_limit limit shouldn't be applied if
CONFIG_HIGHMEM is defined. Your patch looks a bit wrong though, we
need phys_mem.regions[0].size to reflect the total amount of ram we
are going to be using (including high memory). I haven't had a chance
to test the highmem stuff on a machine that has a lot of memory myself
yet.
> Problem: After freeing all init stuff I get a
> Machine check in kernel mode
> Caused by (from: SRR1=81032) Machine check.
> TRAP 0200
> TASK = co1a5ff0[0] 'swapper'
> Last syscall: 120
Well, we would need to know where the machine check happened,
preferably with a stack trace.
Paul.
--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare. Support for the revolution.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-09 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-08 11:55 CONFIG_HIGHMEM problems Tilmann Bitterberg
2000-09-09 9:12 ` Paul Mackerras [this message]
2000-09-12 8:21 ` Tilmann Bitterberg
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=14777.65296.649836.830091@argo.linuxcare.com.au \
--to=paulus@linuxcare.com.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tibit-ibm@bitterberg.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;
as well as URLs for NNTP newsgroup(s).