[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] The linux-based system runs perfectly on vmware, but ke
From: |
Mulyadi Santosa |
Subject: |
Re: [Qemu-devel] The linux-based system runs perfectly on vmware, but kernel panic on qemu |
Date: |
Fri, 18 Jan 2008 18:14:36 +0700 |
Hi...
Pls don't forget to CC qemu-devel too...
On Jan 18, 2008 6:01 PM, Марк Коренберг <address@hidden> wrote:
> I'm not familiar with gdb. but reading ksyms manpage i see that this
> is much simpler to get info from ksyms file, or using ksymoops tool
> rather using gdb.
basically using ksymoops, it will be easier for you to follow stack
trace. But, IMHO, you can do very much the same armed with vmlinux as
a result of gcc -g... just check the nearest symbol address compared
to EIP showed in stack trace.
> If I compile kernel with -g flag, will it print more detailed info in
> "oops!" output ?
Nope.
> Alos, i noticed, that even kqemu enabled, hwclock work fine if run in
> commandline. but not in automatic boot-script. i think some race
> condition or other unknown condition exist. how to debug ? It's very
> easy to reproduce bug. what can i do to detect the problem?
Ehm, I don't know about this one. How about booting in runlevel 1 ?
regards,
Mulyadi.