Hi, > > Any hints how to go on with debugging? > > Use the gdbstub to find out where the kernel is getting > stuck? "Kernel produces no output" just means "we didn't > get far enough through early boot for the kernel to start > sending output to the UART. You might find it useful to > turn on the earlyprintk support, and/or to build the > kernel with debug-UART-via-semihosting and add the > -semihosting argument to the QEMU command line.
earlyprintk doesn't change anything. Ok, that leaves gdb. Stuck here: (gdb) info reg [ ... ] lr 0xc0868bf4 pc 0xc04eee18 Looking them up in System.map finds me: c04eee18 T __loop_delay c0868a28 T panic Ok, so the kernel came successfully though the uncompressing + relocation + enable paging, but paniced before earlyprintk can print something. Guess I'll have to fetch the vmlinux with debug info so I can get a full stack trace and see where it paniced, but not today. cheers, Gerd
