From: "H. Peter Anvin" <hpa@zytor.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Yuhong Bao <yuhongbao_386@hotmail.com>,
chris@csamuel.org, alan@lxorguk.ukuu.org.uk, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: FW: 2.6.38.3 and 2.6.39-rc4 hangs after "Booting the kernel" on quad Pentium Pro system
Date: Sat, 23 Apr 2011 10:51:08 -0700 [thread overview]
Message-ID: <4DB3118C.4030505@zytor.com> (raw)
In-Reply-To: <1303566747.12067.10.camel@localhost.localdomain>
On 04/23/2011 06:52 AM, Thomas Meyer wrote:
>
> so your bios seems to report the size in AX/BX. the code in
> arch/x86/boot/memory.c move the return sizes from CX/DX into AX/BX, when
> CX or DX is not zero.
>
> Could you try to change the line:
>
> } else if (oreg.ax == 15*1024) {
> boot_params.alt_mem_k = (oreg.dx<< 6) + oreg.ax;
>
> to
> } else if (oreg.ax == 15*1024) {
> boot_params.alt_mem_k = (oreg.bx<< 6) + oreg.ax;
>
> That should fix your misdetection.
>
> The assembler code in arch/i386/boot/setup.S seemed to move AX/BX into
> CX/DX, when CX and(!) DX were zero. Then used CX/DX to calc the memory
> size.
>
> PS: gitk --follow arch/x86/boot/memory.c seems to react strangley...
>
Ah yes, this should have been bx; ax/bx and cx/dx forms pairs (unlike
the normal x86 convention of DX:AX and BX:CX forming pairs), and it
doesn't make sense to mix and match them.
-hpa
next prev parent reply other threads:[~2011-04-23 17:52 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 [this message]
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
[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=4DB3118C.4030505@zytor.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@csamuel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas@m3y3r.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 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.