Preinstalled Maverick netbook image won't boot on Gumstix Overo

(Add MLO.)

(Add u-boot.)

Thank you for taking the time to report this bug and help to improve Ubuntu.

It looks like u-boot-omap3 is the package providing the uboot included on this image. Reassigning to that package.

The "Wake up daisy chain activation failed." messages look like kernel messages to me.
Are you sure u-boot-omap3 is the right package?

You're right; sorry, I read too quickly and misunderstood what the issue was, I thought you were saying that you had replaced the uboot and MLO and that this /fixed/ the problem. Sounds like this is the kernel, indeed.

looks like its similar to Bug 594382 ...
which was worked around by disabling CONFIG_CPU_IDLE for beagle a while ago, seems this workaround does not help with gumstix

Same behavior with daily image (http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/current/maverick-preinstalled-netbook-armel+omap.img.gz).

FWIW: Recompiling the kernel with CONFIG_PM disabled makes the issue disappear.

I did a 'git bisect' between Ubuntu-2.6.34-3.10 (good) and Ubuntu-2.6.35-1.1 (bad):

40742fa82ebf53c9367f5807cf1012d518516e74 is first bad commit
commit 40742fa82ebf53c9367f5807cf1012d518516e74
Author: Mike Chan <email address hidden>
Date: Mon May 3 16:04:06 2010 -0700

    OMAP3: PM: Enable IO / IO-CHAIN wakeups for PER

    IO events can also come from GPIO modules, which reside in the PER domain.
    It is possible for the PER to enter RET while CORE is still in ON.
    If GPIO 2-6 are enabled for IO-pad wakeups, the PER domain will not
    wakeup in this case, unless we enable it.

    Signed-off-by: Mike Chan <email address hidden>
    Signed-off-by: Kevin Hilman <email address hidden>

:040000 040000 270b6d5d07c566d7ff1fe6a2d22f7eab3dbf7159 1863e212b840b133e37691c40d3fddabf0f0444e M arch

This patch can be applied on top of Ubuntu-2.6.35-19.28 to revert 40742fa82ebf53c9367f5807cf1012d518516e74 and see that the "daisy chain" issue goes away.

(Note that it is probably not a definitive solution, just a debug help.)

Vincent,

Could I ask you to check whether this bug is also present in the linux-image-2.6.35-1005-linaro-omap kernel package?

Yes, I am afraid the bug is also present for linux-image-2.6.35-1005-linaro-omap_2.6.35-1005.10_armel.deb (see the UART log).

@ogra -- could you confirm whether we would expect this image to work unaltered on this machine? I am under the impression that these images are actually Beagle oriented images?

right, the images are focused on beagle wrt bootloader and kernel, if there is a fix for the kernel thats going upstream soon that makes it easier using the images with less modification it would be a nice to have. nontheless our focus is on beagle XM here and you will definitely have to alter the bootloader even if the kernel works.

CONFIG_MACH_OVERO is set as 'y' at our current omap 3 kernel, so it should work on Overo if the user put the correct x-loader and u-boot at the first disk partition.

Vincent (or any other with an overo board in hands), can you test Natty's image to see if you can still reproduce this issue? x-loader-omap3-overo and u-boot-linaro-omap3-overo should have the needed files to boot the image at Overo.

Ricardo, could you update the package tasks to mention the kernel source package used in the problematic images?

On my side, I've tested Overo with linux-linaro-omap last week and it mostly worked (some issues here and there).

Is this still an issue with the 11.04 release image? If so, please update the bug. Otherwise let it close or see about getting an SRU patch for maverick.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]