public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pre6 BUG oops
Date: Sat, 3 Nov 2001 12:46:57 -0800	[thread overview]
Message-ID: <20011103124657.C5984@twiddle.net> (raw)
In-Reply-To: <3BE03401.406B8585@mandrakesoft.com> <20011031.094112.125896630.davem@redhat.com> <9rpfbj$vrn$1@penguin.transmeta.com> <3BE04338.8F0AF9D4@mandrakesoft.com> <9rpks1$bk$1@penguin.transmeta.com>
In-Reply-To: <9rpks1$bk$1@penguin.transmeta.com>; from torvalds@transmeta.com on Wed, Oct 31, 2001 at 07:53:37PM +0000

On Wed, Oct 31, 2001 at 07:53:37PM +0000, Linus Torvalds wrote:
> I wonder if the "VALID_PAGE(page)" macro is reliable on alpha? You seem
> to be able to trigger this too easily for it to not being something
> specific to the setup..

Should be.  I've never seen an alpha with discontiguous memory.
(Well, I've not looked at a numa box, but that's not at issue here.)

FWIW, we dump the HWRPB memory table early in the boot process, e.g.

memcluster 0, usage 1, start        0, end      192
memcluster 1, usage 0, start      192, end    16267
memcluster 2, usage 1, start    16267, end    16384

where "usage 1" is reserved by the console.


r~

      parent reply	other threads:[~2001-11-03 20:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-31 17:25 pre6 BUG oops Jeff Garzik
2001-10-31 17:41 ` David S. Miller
2001-10-31 18:19   ` Linus Torvalds
2001-10-31 18:30     ` Jeff Garzik
2001-10-31 19:53       ` Linus Torvalds
2001-10-31 21:48         ` 2.4.13 (and 2.4.5) performance drops under load and does not recover David Lang
2001-10-31 23:22           ` David Lang
2001-11-01 21:37             ` David Lang
2001-11-01 22:12               ` ip tables performace problem was " David Lang
2001-11-03 20:46         ` Richard Henderson [this message]

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=20011103124657.C5984@twiddle.net \
    --to=rth@twiddle.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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