All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Magdsick <kmagnum@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu crashes and freezes on x86_64/amd64 host
Date: Fri, 8 Oct 2004 20:22:25 -0400	[thread overview]
Message-ID: <cd8ecdef04100817224ea0b06c@mail.gmail.com> (raw)
In-Reply-To: <1097175246.2833.51.camel@orion>

What is your compiler target when creating the qemu executible?

My understanding is that almost all of the instructions in 64-bit mode
are reverse-compatible with 32-bit mode, but a few have changed
slightly.  If your qemu executible is compiled for 64-bit mode (and is
therefore being run in 64-bit usermode), but the jit is generating
32-bit code, this could be problematic for a small number of
instructions.  I have no direct knowledge of the differences between
the instruction encodings for 32-bit and 64-bit modes, just hearsay.

Just a guess.


-Karl


On Thu, 07 Oct 2004 20:54:06 +0200, Bob Deblier <bob.deblier@telenet.be> wrote:
> Current CVS version, statically compiled, running on FC2 x86_64 (a.k.a.
> amd64)
> 
> Maybe these gdb sessions can help shed some light:
> 
> [bob@orion qemu]$ gdb qemu
> GNU gdb Red Hat Linux (6.0post-0.20040223.19rh)
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "x86_64-redhat-linux-gnu"...Using host
> libthread_db library "/lib64/tls/libthread_db.so.1".
> 
> (gdb) set args -cdrom /opt/iso/w2k.iso -boot d w2k.img
> (gdb) run
> Starting program: /usr/bin/qemu -cdrom /opt/iso/w2k.iso -boot d w2k.img
> 
> Program received signal SIGSEGV, Segmentation fault.
> tb_link_phys (tb=0xbd8dc8, phys_pc=33, phys_page2=426) at
> /home/bob/emulators/cvs/qemu/exec.c:842
> 842         tb->page_next[n] = p->first_tb;
> (gdb)
> 
> Another session crashes at the same location, with different values:
> 
> Program received signal SIGSEGV, Segmentation fault.
> tb_link_phys (tb=0xbd8cf8, phys_pc=33, phys_page2=426) at
> /home/bob/emulators/cvs/qemu/exec.c:842
> 842         tb->page_next[n] = p->first_tb;
> 
> Yet another possibility is that qemu apparently freezes; interrupting
> gdb then gives:
> 
> (gdb) run
> Starting program: /usr/bin/qemu -cdrom /opt/iso/w2k.iso -boot d w2k.img
> 
> Program received signal SIGINT, Interrupt.
> 0x000000000126cd4d in code_gen_buffer ()
> (gdb) where
> #0  0x000000000126cd4d in code_gen_buffer ()
> #1  0x0000000001adbd00 in ?? ()
> #2  0x0000000000446145 in cpu_x86_exec (env1=0xfd76) at
> /home/bob/emulators/cvs/qemu/cpu-exec.c:545
> #3  0x0000000000403294 in main_loop () at
> /home/bob/emulators/cvs/qemu/vl.c:2463
> #4  0x0000000000403fb3 in main (argc=64886, argv=0xc000) at
> /home/bob/emulators/cvs/qemu/vl.c:3392
> (gdb)
> 
> Any pointers welcome.
> 
> Sincerely,
> 
> Bob Deblier
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

  reply	other threads:[~2004-10-09  0:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07 18:54 [Qemu-devel] qemu crashes and freezes on x86_64/amd64 host Bob Deblier
2004-10-09  0:22 ` Karl Magdsick [this message]
2004-10-09  5:29   ` Bob Deblier
2004-10-09 10:08     ` Johannes Schindelin
2004-10-09 12:03       ` Bob Deblier
2004-10-09 14:06         ` Johannes Schindelin
2004-10-09 15:28           ` Bob Deblier
2004-10-09 16:19   ` [Qemu-devel] " Andi Kleen
2004-10-09 18:31     ` Karl Magdsick
2004-10-09 18:38       ` Andi Kleen

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=cd8ecdef04100817224ea0b06c@mail.gmail.com \
    --to=kmagnum@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.