From: Yinghai Lu <yinghai@kernel.org>
To: Anders Eriksson <aeriksson@fastmail.fm>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: Memory probing fails after 2.6.30 (bisected)
Date: Tue, 05 Jan 2010 14:19:23 -0800 [thread overview]
Message-ID: <4B43BAEB.7070308@kernel.org> (raw)
In-Reply-To: <20100105211522.57A3E33C5F5@tippex.mynet.homeunix.org>
On 01/05/2010 01:15 PM, Anders Eriksson wrote:
>
> yinghai@kernel.org said:
>> whole boot log with debug with boot command line?
>>
>>> I can produce a pic of the dmesg for the fingered commit of needed.
>> boot that with earlyprintk=vga please.
>
> I managed to pull this one from the failing boot.
> Does it help?
>
> Linux version 2.6.30-rc2-00450-g8ecee46 (root@korven) (gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) ) #21 SMP Tue Jan 5 10:45:52 CET 2010
> KERNEL supported cpus:
> Intel GenuineIntel
> AMD AuthenticAMD
> NSC Geode by NSC
> Cyrix CyrixInstead
> Centaur CentaurHauls
> Transmeta GenuineTMx86
> Transmeta TransmetaCPU
> UMC UMC UMC UMC
> BIOS-provided physical RAM map:
> BIOS-88: 0000000000000000 - 000000000009f000 (usable)
> BIOS-88: 0000000000100000 - 0000000001000000 (usable)
can you try to revert some e820 detect patch?
bca23db: x86, setup: revert ACPI 3 E820 extended attributes support
df7699c: x86, setup: "glove box" BIOS interrupts in the core boot code
cd67059: x86, setup: guard against pre-ACPI 3 e820 code not updating %ecx
c549e71: x86, setup: ACPI 3, BIOS workaround for E820-probing code
32ec7fd: x86, setup: preemptively save/restore edi and ebp around INT 15 E820
01522df: x86, setup: mark %esi as clobbered in E820 BIOS call
1b72691: x86: fix build warnings in real mode code
c3965bd: x86 boot: proper use of ARRAY_SIZE instead of repeated E820MAX constant
cf9b111: x86: remove pointless comments
829157b: x86: handle BIOSes which terminate e820 with CF=1 and no SMAP
96ae6ea: i386: move boot
4ee5b10: [x86 setup] Correct the SMAP check for INT 0x15, AX=0xe820
2efa33f: [x86 setup] Handle case of improperly terminated E820 chain
449f2ab: Memory probing support for the new x86 setup code
next prev parent reply other threads:[~2010-01-05 22:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 11:02 Anders Eriksson
2010-01-05 19:02 ` Yinghai Lu
2010-01-05 21:15 ` Anders Eriksson
2010-01-05 21:59 ` Bryan Donlan
2010-01-06 8:38 ` Anders Eriksson
2010-01-05 22:19 ` Yinghai Lu [this message]
2010-01-08 14:04 ` Anders Eriksson
2010-01-09 23:03 ` Yinghai Lu
2010-01-10 22:06 ` Anders Eriksson
2010-01-06 0:55 ` Robert Hancock
2010-01-06 8:32 ` Anders Eriksson
2010-01-06 23:53 ` Robert Hancock
2010-01-07 4:04 ` Bryan Donlan
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=4B43BAEB.7070308@kernel.org \
--to=yinghai@kernel.org \
--cc=aeriksson@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome