On Thu, Dec 9, 2010 at 12:34 PM, Alexandre Courbot <gnurou@xxxxxxxxx> wrote: >> > Also, you can use QEmu's GDB server in order to see exactly where your >> > kernel stops executing. This should be much more comfortable than putting >> > printfs into QEmu's code. If you don't know how it works, look here for a >> > short explanation: >> > http://wiki.osdev.org/GDB >> >> Thanks a lot for I was not aware of it. This will surely help. > > Actually that link is not as good as I expected - you will find a much > better step-by-step explanation here (Google cached as the original > does not seem to respond) here: > > http://webcache.googleusercontent.com/search?q=cache:r6sNllBd6GEJ:www.cs.rochester.edu/~sandhya/csc256/assignments/qemu_linux.html > Thanks a lot Alex for finding out the link. I would need to try it now as the newly build kernel is not booting. $ qemu-system-arm -M realview-pbx-a9 -kernel clfskernel-2.6.36 -hda initrd-rootfs.img -append "console=ttyAMA0 root=/dev/hda1 ro mem=256M" -m 1024 -nographic ... VFS: Cannot open root device "hda1" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Backtrace: I assumed this is a block device driver problem, I tried enabling various block device drivers, but no luck so far. May be I should try debugging using the link you just sent. Thanks and Regards, Prasad > If you can run your kernel under QEmu, this will definitely change > your life. You can put breakpoints wherever you want and trace the > system execution from the very beginning, which is invaluable for bugs > like the one you had. > > Alex. > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
