Regression in 2.6.23-pre Was: Problems with 2.6.23-rc6 on AMD Geode LX800

From: Joerg Pommnitz
Date: Wed Sep 26 2007 - 07:03:19 EST

Hello all,
this is what git bisect told me about the problem:

jpo@jpo-laptop:~/linux-2.6$ git bisect good
4fd06960f120e02e9abc802a09f9511c400042a5 is first bad commit
commit 4fd06960f120e02e9abc802a09f9511c400042a5
Author: H. Peter Anvin <hpa@xxxxxxxxx>
Date: Wed Jul 11 12:18:56 2007 -0700

Use the new x86 setup code for i386

This patch hooks the new x86 setup code into the Makefile machinery. It
also adapts boot/tools/build.c to a two-file (as opposed to three-file)
universe, and simplifies it substantially.

Signed-off-by: H. Peter Anvin <hpa@xxxxxxxxx>
Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>

:040000 040000 6560eb5b7e40d93813276544bced8c478f9067f5 fe5f90d9ca08e526559815789175602ba2c51743 M arch



----- Ursprüngliche Mail ----
Von: Jordan Crouse <jordan.crouse@xxxxxxx>
An: Joerg Pommnitz <pommnitz@xxxxxxxxx>
CC: cebbert@xxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx
Gesendet: Dienstag, den 25. September 2007, 17:04:52 Uhr
Betreff: Re: Problems with 2.6.23-rc6 on AMD Geode LX800

On 25/09/07 01:38 -0700, Joerg Pommnitz wrote:
> Chuck, Jordan,
> thanks for taking an interest in this problem. As suggested by Jordan I tried a new
> BIOS revision from
> Unfortunately the kernel still fails to boot in the same way.

You'll have to contact Digital Logic and have them check with the BIOS vendor
to see if the fix was made in that version or not. I don't have that
particular board, so I can't try out the fixes here.

I'm still trying to track down the particulars of the fix from the BIOS
vendor. I'll let you know.

> Do you still need the disassembled reserve_bootmem_core?

Sure - you might as well - just to make sure its the same problem.


Jordan Crouse
Systems Software Development Engineer
Advanced Micro Devices, Inc.

Yahoo! Clever: Sie haben Fragen? Yahoo! Nutzer antworten Ihnen.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at