As title. Log from a locally modified abuild attached.
I think this is something we did some time ago with simplifying
debugging facility - trying to use printk() everywhere.
I have seen i440bx build break similarly. You don't see it in this log
because I am developing a fix for it. (Working mainly on a P2B-LS, I'm
directly affected :-) )
i440lx uses a similar debugging facility and theoretically is also
broken, but apparently there is no 440LX mainboards in the tree.
abuild is modified as below, just to get CONFIG_DEBUG_RAM_SETUP set
when doing all-targets abuild:
--- util/abuild/abuild (revision 6204)
+++ util/abuild/abuild (working copy)
@@ -58,6 +58,9 @@
# use ccache
+# RAM debug messages
# stackprotect mode enabled by -ns option.
@@ -197,6 +200,11 @@
echo "CONFIG_CCACHE=y" >>
+ if [ "$debugramsetup" = "true" ]; then
+ printf "(debugramsetup enabled) "
+ echo "CONFIG_DEBUG_RAM_SETUP=y" >>
if [ "$scanbuild" = "true" ]; then
printf "(scan-build enabled) "
echo "CONFIG_SCANBUILD_ENABLE=y" >>
Above is not meant to be committed, but just in case, it is
Signed-off-by: Keith Hui <buurin(a)gmail.com>