qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Mulyadi Santosa" <mulyadi.santosa@gmail.com>
To: "Марк Коренберг" <socketpair@gmail.com>
Cc: qemu-devel@nongnu.org
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	[thread overview]
Message-ID: <f284c33d0801180314r421da6cfjf3b7f6c25175d246@mail.gmail.com> (raw)
In-Reply-To: <b8f627e0801180301o23b07c89pcf08717f2450dcf4@mail.gmail.com>

Hi...

Pls don't forget to CC qemu-devel too...

On Jan 18, 2008 6:01 PM, Марк Коренберг <socketpair@gmail.com> 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.

  parent reply	other threads:[~2008-01-18 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 11:50 [Qemu-devel] The linux-based system runs perfectly on vmware, but kernel panic on qemu Марк Коренберг
2008-01-18  2:21 ` Mulyadi Santosa
     [not found]   ` <b8f627e0801180210h6abce895yeede4f9950534dc@mail.gmail.com>
2008-01-18 10:17     ` Mulyadi Santosa
     [not found]       ` <b8f627e0801180301o23b07c89pcf08717f2450dcf4@mail.gmail.com>
2008-01-18 11:14         ` Mulyadi Santosa [this message]
     [not found]           ` <b8f627e0801180339y390ba860rb05b6fde5bb6502b@mail.gmail.com>
2008-01-18 12:22             ` Mulyadi Santosa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f284c33d0801180314r421da6cfjf3b7f6c25175d246@mail.gmail.com \
    --to=mulyadi.santosa@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=socketpair@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).