On Wed, Mar 18, 2009 at 01:42:56PM -0600, Myles Watson wrote: > On Wed, Mar 18, 2009 at 1:31 PM, Ward Vandewege <[email protected]> wrote: > > On Wed, Mar 18, 2009 at 12:38:34PM -0600, Myles Watson wrote: > >> On Wed, Mar 18, 2009 at 12:17 PM, Myles Watson <[email protected]> wrote: > >> > On Tue, Mar 17, 2009 at 3:27 PM, Myles Watson <[email protected]> wrote: > >> >> I have two coreboot trees. As far as I can tell they're identical. > >> >> One produces working ROM images, and the other reboots when it jumps > >> >> to the payload. > >> > > >> > That was the key. I hadn't done a make clean in the working tree. > >> > Rev 4000 broke it for me, but I'm still not sure why. Once I was > >> > doing make clean every time I could find the revision that was > >> > breaking. It looks like Rev 4000 changed the compile flags, so that's > >> > where I'm going next. Everything else in 4000 looks innocuous to me. > >> > >> The question is why these compiler flags for coreboot make SeaBIOS > >> panic. I'm still trying to narrow it down, but if you spot it first > >> that would be great! > > > > FWIW, I'm seeing the exact same thing (reboot when jump to payload) with a > > filo payload and the latest coreboot tree (patched for m2a-vm): > > Thanks! That helps to know it's not just seabios. If you remove > -fno-frame-pointer it should work again.
Confirmed, removing -fomit-frame-pointer fixes the boot with FILO. Thanks! Ward. -- First Annual Libre Planet on March 21/22 2009: http://fsf.org/conference Ward Vandewege <[email protected]> Free Software Foundation - Senior Systems Administrator -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
