From: Michael Frank <mhf@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: 2.4.25-rc1: BUG: wrong zone alignment, it will crash
Date: Fri, 6 Feb 2004 18:34:08 +0800 [thread overview]
Message-ID: <200402061735.07726.mhf@linuxmail.org> (raw)
As with 2.4.24, using the highmem option causes the BUG message.
This is a kernel ex BK without any patches.
Linux version 2.4.25-rc1 (root@mhfl4) (gcc version 2.95.3 20010315 (release)) #5 Fri Feb 6 17:27:18 HKT 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001eff0000 (usable)
BIOS-e820: 000000001eff0000 - 000000001eff3000 (ACPI NVS)
BIOS-e820: 000000001eff3000 - 000000001f000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
300MB HIGHMEM available.
195MB LOWMEM available.
On node 0 totalpages: 126960
zone(0): 4096 pages.
zone(1): 46064 pages.
zone(2): 76800 pages.
BUG: wrong zone alignment, it will crash
Kernel command line: vga=0xf07 root=/dev/hda4 console=tty0 console=ttyS0,115200n8r devfs=nomount nousb acpi=off highmem=300m
Initializing CPU#0
Detected 2399.771 MHz processor.
Console: colour VGA+ 80x60
Calibrating delay loop... 4784.12 BogoMIPS
Memory: 498696k/507840k available (1589k kernel code, 8756k reserved, 676k data, 120k init, 307200k highmem)
The kernel seems to experience stability problems.
How to resolve?
Michael
next reply other threads:[~2004-02-06 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 10:34 Michael Frank [this message]
2004-02-06 13:44 ` 2.4.25-rc1: BUG: wrong zone alignment, it will crash Marcelo Tosatti
2004-02-06 14:45 ` Michael Frank
2004-02-06 15:36 ` Rik van Riel
2004-02-06 16:46 ` Michael Frank
2004-02-06 17:07 ` Randy.Dunlap
2004-02-06 18:35 ` Michael Frank
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=200402061735.07726.mhf@linuxmail.org \
--to=mhf@linuxmail.org \
--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 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.