Messages in this thread | | | Date | Tue, 05 Jan 2010 14:19:23 -0800 | From | Yinghai Lu <> | Subject | Re: Memory probing fails after 2.6.30 (bisected) |
| |
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
| |