From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1AxTJx-00079t-Rb for qemu-devel@nongnu.org; Sun, 29 Feb 2004 10:57:37 -0500 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1AxTJQ-00074Y-60 for qemu-devel@nongnu.org; Sun, 29 Feb 2004 10:57:36 -0500 Received: from [209.123.232.253] (helo=zero.voxel.net) by monty-python.gnu.org with esmtp (Exim 4.30) id 1AxTJP-00074U-VW for qemu-devel@nongnu.org; Sun, 29 Feb 2004 10:57:04 -0500 Received: from dsdk12.net (alb-24-195-230-60.nycap.rr.com [24.195.230.60]) by zero.voxel.net (Postfix) with ESMTP id E2F3B267A83 for ; Sun, 29 Feb 2004 10:56:59 -0500 (EST) Message-ID: <40420BAA.5040107@dsdk12.net> Date: Sun, 29 Feb 2004 10:56:26 -0500 From: Derrik Pates MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] qemu SEGV in ide.c:1057 Reply-To: qemu-devel@nongnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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