Can't boot with 2011.05
Since the 2011.05 Buildroot release I've not been able to get a bootable system even with the simplest of options and I haven't a clue why. In 2011.02 if I was to have some simple options of a i386 build platform targeting i686 to generate an initramfs system (everything else default, kernel with i386 defconfig) the system would boot fine in QEMU or VirtualBox and give me a login prompt. Trying a similar approach on 2011.05 either chucks a "Adjusting TSC clocksource" and hang or a "ip used greatest stack depth" and hang. I assume this is not the actual cause of the hang but what I see before the problem, which I think is to do with mounting the root file system.
I am wondering what's changed that might be causing this,
Thanks
Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110726/8cfd8755/attachment-0001.html>
Quoted 13 lines · Sam Nazarko
Since the 2011.05 Buildroot release I've not been able to get a bootable system even with the simplest of options and I haven't a clue why. In 2011.02 if I was to have some simple options of a i386 build platform targeting i686 to generate an initramfs system (everything else default, kernel with i386 defconfig) the system would boot fine in QEMU or VirtualBox and give me a login prompt. Trying a similar approach on 2011.05 either chucks a "Adjusting TSC clocksource" and hang or a "ip used greatest stack depth" and hang. I assume this is not the actual cause of the hang but what I see before the problem, which I think is to do with mounting the root file system.
Quoted 2 lines
I am wondering what's changed that might be causing this,
Hard to tell exactly from the information given, but....
I recall that the old default choice for Intel (i386) was changed to default to i586.
Which was done to support NPTL builds. (cmpxchg instruction used).
Other than that change specific to Buildroot;
Any change in toolchain version;
C library version and/or type of C library;
Any change in kernel version;
Might, anyone of them, cause the problem "as reported".
Mike
Quoted 9 lines
Thanks
Sam