public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "D. Stimits" <stimits@idcomm.com>
To: kernel-list <linux-kernel@vger.kernel.org>
Subject: page reserved twice
Date: Tue, 03 Jul 2001 18:19:27 -0600	[thread overview]
Message-ID: <3B42610F.29D004FF@idcomm.com> (raw)

I'm curious if there is any significance to this, which occurs at each
reboot on an SMP system running noapic (sometimes Netscape manages to
produce a hard lockup on the system, sometimes a core dump indicates NS
had signal 7, bus error, in cases where it doesn't lock the system),
2.4.6-pre1 with XFS patches:

 kernel: BIOS-provided physical RAM map:
 kernel:  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 kernel:  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 kernel:  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 kernel:  BIOS-e820: 0000000000100000 - 000000000ffe0000 (usable)
 kernel:  BIOS-e820: 000000000ffe0000 - 000000000fff8000 (ACPI data)
 kernel:  BIOS-e820: 000000000fff8000 - 0000000010000000 (ACPI NVS)
 kernel: Scan SMP from c0000000 for 1024 bytes.
 kernel: Scan SMP from c009fc00 for 1024 bytes.
 kernel: Scan SMP from c00f0000 for 65536 bytes.
 kernel: found SMP MP-table at 000faf50
 kernel: hm, page 000fa000 reserved twice.
 kernel: hm, page 000fb000 reserved twice.
 kernel: hm, page 000f4000 reserved twice.
 thanteros kernel: hm, page 000f5000 reserved twice.
 thanteros kernel: On node 0 totalpages: 65504
 thanteros kernel: zone(0): 4096 pages.
 kernel: zone(1): 61408 pages.
 kernel: zone(2): 0 pages.
 kernel: Intel MultiProcessor Specification v1.1
 kernel:     Virtual Wire compatibility mode.
 kernel: OEM ID: _AMI_    Product ID: 840_CARMEL__ APIC at: 0xFEE00000


Very similar messages seem to occur on a different machine with RH's
2.4.2 kernel, BX chipset, and IO-APIC enabled. The machine this is from
has had this message on earlier kernels as well, none of which had XFS
patches. What is the significance (or consequence) of pages reserved
twice?

D. Stimits, stimits@idcomm.com

             reply	other threads:[~2001-07-04  0:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-04  0:19 D. Stimits [this message]
2001-07-04  6:57 ` page reserved twice michaelc
2001-07-04  7:02 ` michaelc
  -- strict thread matches above, loose matches on Subject: below --
2001-07-04  7:06 michaelc

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=3B42610F.29D004FF@idcomm.com \
    --to=stimits@idcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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