qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Derrik Pates <dpates@dsdk12.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu SEGV in ide.c:1057
Date: Sun, 29 Feb 2004 10:56:26 -0500	[thread overview]
Message-ID: <40420BAA.5040107@dsdk12.net> (raw)

Ok, I've been playing with installing Win2k in qemu - the installer gets 
started, but it always SEGVs during device detection. It appears Win2k's 
trying to probe for all available IDE interfaces, and there's a bogus 
address in the data structure for interface number 6.

#0  ide_ioport_write (env=0x10b930d8, addr=6, val=160)
     at /misc/tmp/qemu/ide.c:1057
1057        IDEState *s = ide_if->cur_drive;
(gdb) bt
#0  ide_ioport_write (env=0x10b930d8, addr=6, val=160)
     at /misc/tmp/qemu/ide.c:1057
#1  0x10002f08 in cpu_outb (env=0x10b930d8, addr=248, val=160)
     at /misc/tmp/qemu/vl.c:300
#2  0x1081e064 in code_gen_buffer ()
#3  0x1002183c in cpu_x86_exec (env1=0x10b930d8)
     at /misc/tmp/qemu/cpu-exec.c:482
#4  0x10006a10 in main_loop (opaque=0x10b930d8) at /misc/tmp/qemu/vl.c:3001
#5  0x100075b4 in main (argc=268763136, argv=0x7ffff2b0)
     at /misc/tmp/qemu/vl.c:3619

(gdb) print addr
$1 = 6
(gdb) print ide_if
$2 = (IDEState *) 0xff00aa55
(gdb) print ide_if->cur_drive
Cannot access memory at address 0xff00aa89

This is from the core file it generated, using 'gdb ./qemu core' to 
analyze the core dump. Up until this point, Windows 2000 runs fine 
(though very slowly). Suggestions on what I can do to fix this, patches, 
etc. are welcomed. I'll try to dig around in the code myself and see 
what I can figure out.

--
Derrik Pates
dpates@dsdk12.net

                 reply	other threads:[~2004-02-29 15:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40420BAA.5040107@dsdk12.net \
    --to=dpates@dsdk12.net \
    --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 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).