Hi Juha, Nice to receive your instruction so soon. :) Unfortunately, it doesn't work. :(
I have tried "-clock unix", and the result is the same as before. And then I got the log by "-monitor stdio" option. Here I pasted the last few lines. You can find the full contents from the attached file. <4>[ 0.000000] Mount-cache hash table entries: 512 <6>[ 0.000000] CPU: Testing write buffer coherency: ok <6>[ 0.000000] regulator: core version 0.5 <6>[ 0.000000] NET: Registered protocol family 16 <7>[ 0.000000] mux: Setting signal i2c2_scl.i2c2_scl 0x0100 -> 0x0100 <7>[ 0.000000] mux: Setting signal i2c2_sda.i2c2_sda 0x0100 -> 0x0100 <7>[ 0.000000] mux: Setting signal i2c3_scl.i2c3_scl 0x0100 -> 0x0100 <7>[ 0.000000] mux: Setting signal i2c3_sda.i2c3_sda 0x0100 -> 0x0100 <7>[ 0.000000] mux: Setting signal sdrc_cke0.sdrc_cke0 0x0018 -> 0x0000 <7>[ 0.000000] mux: Setting signal sdrc_cke1.sdrc_cke1 0x0018 -> 0x0000 <6>[ 1.405792] OMAP DMA hardware revision 4.0 <7>[ 1.407684] mux: Setting signal dss_data20.gpio90 0x0014 -> 0x0004 <4>[ 1.433105] bio: create slab <bio-0> at 0 <6>[ 1.446685] usbcore: registered new interface driver usbfs <6>[ 1.447845] usbcore: registered new interface driver hub <6>[ 1.448791] usbcore: registered new device driver usb <6>[ 1.450775] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2200 kHz Can you help to tell what is the problem? I don't understand the log. Or you can give some more hints on it. And, I have tried on another version downloaded from the repo truck weekly build directory. Hardwere error occurs. See message below: Also, can you help on explaining the message? Thank you! " Uncompressing Linux... done, booting the kernel. qemu: hardware error: twl4030_4b_write: unknown register 0xce value 0x08 CPU #0: R00=00000002 R01=00000007 R02=fa070000 R03=0000001c R04=cfc42080 R05=00005000 R06=00000000 R07=00000000 R08=00000001 R09=00000008 R10=0000024a R11=0000601f R12=cfc1fab0 R13=cfc1fa90 R14=c0083a74 R15=c01f9c88 PSR=60000193 -ZC- A svc32 Aborted (core dumped) " On Tue, Aug 3, 2010 at 1:19 PM, <[email protected]> wrote: > > On Aug 3, 2010, at 04:36, ext Sylvia Liu wrote: > >> I have tried your method exactly as you said, but the qemu stopped here: >> >> [ 0.238] Loading kernel image info >> Loading kernel (1802 kB)... done in 72 ms (24958 kB/s) >> [ 0.308] Loading initfs image info >> [ 0.308] Total bootup time 339 ms >> [ 0.310] Serial console enabled >> Uncompressing Linux... done, booting the kernel. >> >> Seems the uncompressing transaction is too fast. >> How can I get more information about it? >> Do you know how to resolve it? > > This is exactly how it should look like, apart from stopping there of course > ;) > > Are you running qemu on linux? If so, add "-clock unix" on the qemu command > line, that should do the trick. Sorry I forgot that from the original mail. > > If the above doesn't help, replace "-serial stdio" with "-monitor stdio" on > the qemu command line, and when the emulation stops enter "pmemsave > 0x80399a44 0x8000 log" in the qemu monitor console. This will save the early > boot log of the kernel in a file named "log" and from there you will be able > to see where the boot stops. Note the address is valid for this particular > kernel build only. > > > Regards, > Juha > > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev >
boot_stop.log
Description: Binary data
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
