Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Florian Lohoff <flo@rfc822.org>, linux-mips@oss.sgi.com
Subject: Re: crash in __alloc_bootmem_core on SGI current cvs
Date: Tue, 16 Jan 2001 14:24:49 -0200	[thread overview]
Message-ID: <20010116142449.B13302@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010116170209.5546K-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Tue, Jan 16, 2001 at 05:06:29PM +0100

On Tue, Jan 16, 2001 at 05:06:29PM +0100, Maciej W. Rozycki wrote:

> On Tue, 16 Jan 2001, Ralf Baechle wrote:
> 
> > > Before:
> > > 	On node 0 totalpages: 589824
> > > 	zone(0): 589824 pages.
> > > 
> > > 
> > > After:
> > > 	On node 0 totalpages: 65536
> > > 	zone(0): 65536 pages.
> > 
> > I probably already got used too machines with gigs of memory to notice ;-)
> 
>  The number actually denotes the highest page, regardless of the number of
> pages, so you only need a single page placed far away from address zero to
> observe such large counts.

The Indy has it's memory starting at phys. 0x08000000; a part of it is also
mirrored at physical address zero.  So in case of an Indy the totalpages
number should indicate 128mb too much which means that Flo's machine should
have only 128mb real memory.  Right Florian?

> > Can you decode the addresses in $epc and $31 for me?
> 
>  Probably a memory access in free_all_bootmem() or so.

   Ralf

  reply	other threads:[~2001-01-16 16:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15 17:11 crash in __alloc_bootmem_core on SGI current cvs Florian Lohoff
2001-01-15 21:21 ` Maciej W. Rozycki
2001-01-16  8:10   ` Ralf Baechle
2001-01-16 14:36   ` Florian Lohoff
2001-01-16 15:57     ` Ralf Baechle
2001-01-16 16:06       ` Maciej W. Rozycki
2001-01-16 16:24         ` Ralf Baechle [this message]
2001-01-16 16:34           ` Maciej W. Rozycki
2001-01-16 19:23             ` Ralf Baechle
2001-01-16 19:47               ` Maciej W. Rozycki
2001-01-16 20:04                 ` Ralf Baechle
2001-01-16 16:44           ` Florian Lohoff
2001-01-16 16:28         ` Florian Lohoff
2001-01-16 16:39           ` Maciej W. Rozycki
2001-01-16 19:22             ` Ralf Baechle
2001-01-17 13:15               ` Kanoj Sarcar
2001-01-17 13:15                 ` Kanoj Sarcar
2001-01-16 16:01     ` Maciej W. Rozycki
2001-01-16 16:08       ` Maciej W. Rozycki
2001-01-16 16:49       ` Florian Lohoff
2001-01-16 18:48         ` Florian Lohoff
2001-01-16 19:52           ` Maciej W. Rozycki
2001-01-16 23:03             ` Florian Lohoff
  -- strict thread matches above, loose matches on Subject: below --
2001-01-16 16:55 Ian Chilton
2001-01-16 17:06 ` Maciej W. Rozycki
2001-01-16 19:14 ` Ralf Baechle
2001-01-16 19:38   ` Maciej W. Rozycki
2001-01-16 16:56 tmaloney
2001-01-16 16:59 Ian Chilton

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=20010116142449.B13302@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=flo@rfc822.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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