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

2014-12-03 Thread Rolf Leggewie
natty has seen the end of its life and is no longer receiving any updates. Marking the natty task for this ticket as "Won't Fix". ** Changed in: gcc-4.5 (Ubuntu Natty) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is su

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

2014-06-12 Thread Michael Collison
** Changed in: gcc-linaro Assignee: (unassigned) => Michael Collison (michael-collison) ** Changed in: gcc-linaro Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/b

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

2012-01-27 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcc-4.5 (Ubuntu Natty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683683 Title:

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

2012-01-27 Thread 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683683 Title: run

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

2011-01-10 Thread Jamie Bennett
** Changed in: gcc-linaro Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683683 Title: run-init on omap3, omap4 in natty dies if busybox is built with -marm -- ubun

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

2010-12-07 Thread Dave Martin
I don't have the right filesystem in front of me to debug, but this recipe should work for debugging PID 1 with gdb (assuming you have a platform already set up with a populated root filesystem etc.): Connect a keyboard and monitor before booting. Boot with rdinit=/bin/sh console= mkdir /proc /s

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

2010-12-06 Thread Oliver Grawert
@dave, ah, thanks, yeah, we should retarget it if that patch is complete now (note that this bug is just exposing a busybox issue, the run-init error is apparently just a side effect of exec misbehaving if busybox is built with -marm) -- You received this bug notification because you are a member

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

2010-12-06 Thread Dave Martin
@michael - rdinit=/bin/sh is highly use for initramfs debugging too if you're not aware -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683683 Title: run-init on omap3, omap4 in natty dies if busybox

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

2010-12-06 Thread Dave Martin
@ogra, there is a bug open on klibc -- the one I referenced above: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/527720 Does it need to be prodded? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs

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

2010-12-06 Thread Oliver Grawert
@michael,if you only want to debug a running initrd you dont need to repack it, just boot with the break= option (some of the valid values are: top, premount, bottom). that way you can get a shell inside the initrd, do your debugging tasks and go on booting with ctrl-D note though that in case

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

2010-12-06 Thread Oliver Grawert
@dave, could you open a new bug for klibc ? this bug is not klibc related. busybox-initramfs links against glibc and given that busybox' exec behavior changes if we use -marm or not this one is rather a toolchain one. -- You received this bug notification because you are a member of Ubuntu Bugs,

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

2010-12-06 Thread Jamie Bennett
On 6 Dec 2010, at 03:33, Michael Hope <683...@bugs.launchpad.net> wrote: > I'm a bit of a initrd newbie so I wrote up the steps in testing under QEMU > here: > https://wiki.linaro.org/MichaelHope/Sandbox/DebuggingOnInitrd Great resource Michael, thanks for putting it together. -- You received

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

2010-12-05 Thread Michael Hope
I'm a bit of a initrd newbie so I wrote up the steps in testing under QEMU here: https://wiki.linaro.org/MichaelHope/Sandbox/DebuggingOnInitrd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683683 Tit

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

2010-12-03 Thread Dave Martin
klibc has some outstanding ARM/Thumb interworking issues ... can someone please apply the patch from this bug: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/527720 (thumb2 porting issues identified: klibc uses mov.*pc) ... and see if it makes any difference? -- You received this bug not

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

2010-12-03 Thread Oliver Grawert
** Summary changed: - run-init on omap3, omap4 in natty dies with "run-init: Unknown error 17718852" + run-init on omap3, omap4 in natty dies if busybox is built with -marm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.