From: Chris Samuel <chris@csamuel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yuhong Bao <yuhongbao_386@hotmail.com>,
alan@lxorguk.ukuu.org.uk, tglx@linutronix.de, mingo@redhat.com,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.38.3 and 2.6.39-rc4 hangs after "Booting the kernel" on quad Pentium Pro system
Date: Sat, 23 Apr 2011 16:43:54 +1000 [thread overview]
Message-ID: <201104231643.55372.chris@csamuel.org> (raw)
In-Reply-To: <4DB2338B.5030803@zytor.com>
[-- Attachment #1: Type: Text/Plain, Size: 898 bytes --]
On Sat, 23 Apr 2011 12:03:55 PM H. Peter Anvin wrote:
> I suspect this broke during the rewrite of the setup code to
> C in 2007.
Looking at arch/x86/boot/memory.c I see the snipped:
} else {
/*
* This ignores memory above 16MB if we have a memory
* hole there. If someone actually finds a machine
* with a memory hole at 16MB and no support for
* 0E820h they should probably generate a fake e820
* map.
*/
boot_params.alt_mem_k = oreg.ax;
}
Could this be what's going on ? Or am I just grasping at straws ? :-)
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2011-04-23 6:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 13:33 2.6.38.3 and 2.6.39-rc4 hangs after "Booting the kernel" on quad Pentium Pro system Chris Samuel
2011-04-22 13:46 ` Ingo Molnar
2011-04-22 19:09 ` Yinghai Lu
2011-04-22 19:29 ` Ingo Molnar
2011-04-22 19:46 ` Yinghai Lu
2011-04-23 0:20 ` Chris Samuel
2011-04-22 16:34 ` Alan Cox
2011-04-23 0:16 ` Chris Samuel
2011-04-23 1:28 ` Yuhong Bao
2011-04-23 1:35 ` Chris Samuel
2011-04-23 1:46 ` Yuhong Bao
2011-04-23 2:26 ` H. Peter Anvin
2011-04-23 2:31 ` Yuhong Bao
2011-04-23 4:33 ` Chris Samuel
2011-04-23 5:22 ` Chris Samuel
[not found] ` <SNT125-W25B0C502FF72465BC6B55BC3940@phx.gbl>
[not found] ` <201104231855.47680.chris@csamuel.org>
2011-04-23 10:47 ` FW: " Yuhong Bao
2011-04-23 13:52 ` Thomas Meyer
2011-04-23 17:51 ` H. Peter Anvin
2011-04-23 23:24 ` Chris Samuel
2011-04-24 0:16 ` Chris Samuel
2011-04-24 0:22 ` Chris Samuel
2011-04-24 8:46 ` Yinghai Lu
2011-04-25 11:13 ` Chris Samuel
2011-04-25 23:25 ` [tip:x86/urgent] x86, setup: When probing memory with e801, use ax/bx as a pair tip-bot for H. Peter Anvin
2011-04-26 4:50 ` Chris Samuel
2011-04-26 8:12 ` Ingo Molnar
2011-04-27 3:30 ` Chris Samuel
2011-05-05 11:57 ` Chris Samuel
2011-05-05 12:10 ` Ingo Molnar
2011-05-06 11:47 ` Chris Samuel
2011-05-06 12:04 ` Ingo Molnar
2011-05-06 12:10 ` Chris Samuel
2011-05-30 4:54 ` Yuhong Bao
2011-04-23 2:03 ` 2.6.38.3 and 2.6.39-rc4 hangs after "Booting the kernel" on quad Pentium Pro system H. Peter Anvin
2011-04-23 6:43 ` Chris Samuel [this message]
[not found] ` <1ac2dd46-0677-4be6-aca0-f8787da34cee@email.android.com>
2011-04-23 1:36 ` Chris Samuel
2011-04-23 9:35 ` Alan Cox
2011-04-23 10:35 ` Chris Samuel
2011-04-23 11:32 ` Chris Samuel
2011-04-23 13:11 ` Chris Samuel
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=201104231643.55372.chris@csamuel.org \
--to=chris@csamuel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yuhongbao_386@hotmail.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;
as well as URLs for NNTP newsgroup(s).