[U-Boot] [STATUS] v2009.11-rc1 is out

[Detlev Zundel <dzu@denx.de>]

Hi rhabarber1848,

> I just tested it on my Dbox2 board where U-Boot 2009.08 is working 
> perfectly well with unchanged config.
> But now U-Boot raises an exception during machine check:
>
> =============================================================================
> U-Boot 2009.11 (Tuxbox) (Nov 03 2009 - 08:59:24)
>
> CPU:   PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
> Board: DBOX2, Sagem, BMon V1.0
>        Watchdog enabled
> I2C:   ready
> DRAM:  64 MB
> Top of RAM usable for U-Boot at: 04000000
> Reserving 201k for U-Boot at: 03fcd000
> Reserving 144k for malloc() at: 03fa9000
> Reserving 60 Bytes for Board Info at: 03fa8fc4
> Reserving 52 Bytes for Global Data at: 03fa8f90
> Stack Pointer at: 03fa8f78
> New Stack Pointer is: 03fa8f78
> Now running in RAM - U-Boot at: 03fcd000
> FLASH:  8 MB
> FB:    ready
> Bus Fault @ 0x03fcfe0c, fixup 0x00000000
> Machine check in kernel mode.
> Caused by (from msr): regs 03fa8d88 Unknown values in msr
> NIP: 03FCFE0C XER: 8000007F LR: 03FCFD98 REGS: 03fa8d88 TRAP: 0200 DAR: 3038B700
> MSR: 00001002 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
>
> GPR00: 30323030 03FA8E78 03FA8F90 00000008 30323030 30376666 00000000 000686CC
> GPR08: 03FF56CC 3038B6FC 00000002 000F423F FF002848 00031CBC 03FFB600 03F8D000
> GPR16: 00000000 00000000 00000000 00000000 20004000 00000001 60634001 90640170
> GPR24: 03FA8F90 00000040 03FCD000 00000000 0006868C 00000001 03FFB678 03FCD000
> Call backtrace:
> machine check
> =============================================================================
>
> The remaining boot messages would be:
>
> In:    serial
> Out:   serial
> Err:   serial
> Net:   SCC ETHERNET
> LCD:   ready
>
> Any pointers where I could start debugging?

Grepping through my source, I cannot find such a configuration - do you
plan to submit this support here sometime?

Apart from that, I'd strongly start looking for implications of the
recent rewrite of the relocation strategy to code not in mainline.
Given that the last message is "FB:" (also not in mainline), the
corresponding code would be my start for the debugging.

Apart from that you could also use the information in our DULG[1] for
debugging of U-Boot after relocation and use gdb to find the code
corresponding to "0x3fcfe0c".  You'll not even need a JTAG debugger for
this address lookup as all neccessary informations are in your dump ;)

Cheers
  Detlev

[1] http://www.denx.de/wiki/view/DULG/DebuggingUBoot#Section_10.1.2.

-- 
Man is a fool, and woman, for tolerating him, is a damned fool
                       -- Mark Twain
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de