[Bug 683683] Re: run-init on omap3, omap4 in natty dies if busybox is built with -marm

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gcc-4.5 (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-4.5 in Ubuntu.
https://bugs.launchpad.net/bugs/683683

Title:
  run-init on omap3, omap4 in natty dies if busybox is built with -marm

Status in Linaro GCC:
  Incomplete
Status in “busybox” package in Ubuntu:
  Fix Released
Status in “gcc-4.5” package in Ubuntu:
  Confirmed
Status in “klibc” package in Ubuntu:
  Invalid
Status in “busybox” source package in Natty:
  Fix Released
Status in “gcc-4.5” source package in Natty:
  Confirmed
Status in “klibc” source package in Natty:
  Invalid

Bug description:
  trying to boot a natty image on the omap4 platform works fine for teh
  first part where jasper-initramfs resizes, configures and reboots teh
  system. as soon as the reboot happened and the rootfs is trying to be
  mounted the boot dies with:

  /init: exec: line 331: run-init: Unknown error 17718852

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-linaro/+bug/683683/+subscriptions