On 07.11.2008 04:15, Carl-Daniel Hailfinger wrote: > We are woefully unaware about how much stack v3 really uses. > This is a complete rewrite of my earlier stack checker. It works for CAR > and RAM, has better abstraction and actually gives us nice results. > The stack checker is default off due to its rather measurable impact on > boot speed. > Diagnostic messages are printed on first initialization, directly after > RAM init and directly before passing control to the payload. Sample qemu > log is attached. Extract from that log follows: > > coreboot-3.0.986 Fri Nov 7 04:04:37 CET 2008 starting... > (console_loglevel=8) > Initial lowest stack is 0x0008fe98 > Choosing fallback boot. > [...] > Done RAM init code > After RAM init, lowest stack is 0x0008fe30 > Done printk() buffer move > [...] > LAR: load_file_segments: Failed for normal/payload > Before handoff to payload, lowest stack is 0x0008bf50 > FATAL: No usable payload found. > > Signed-off-by: Carl-Daniel Hailfinger <[EMAIL PROTECTED]> >
Ping? Regards, Carl-Daniel -- http://www.hailfinger.org/ -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
