From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=47162 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OUj6v-0008Sm-FK for qemu-devel@nongnu.org; Fri, 02 Jul 2010 12:29:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OUj6u-00008b-DL for qemu-devel@nongnu.org; Fri, 02 Jul 2010 12:29:05 -0400 Received: from david.siemens.de ([192.35.17.14]:15636) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OUj6u-00008B-4X for qemu-devel@nongnu.org; Fri, 02 Jul 2010 12:29:04 -0400 Message-ID: <4C2E13CB.2020009@siemens.com> Date: Fri, 02 Jul 2010 18:28:59 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20100617095222.20761.57447.malonedeb@wampee.canonical.com> <20100702100920.24319.7675.malone@palladium.canonical.com> In-Reply-To: <20100702100920.24319.7675.malone@palladium.canonical.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Re: [Bug 595438] Re: KVM segmentation fault, using SCSI+writeback and linux 2.4 guest List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: socketpair@gmail.com Cc: qemu-devel@nongnu.org, Bug 595438 <595438@bugs.launchpad.net> =D0=9A=D0=BE=D1=80=D0=B5=D0=BD=D0=B1=D0=B5=D1=80=D0=B3 =D0=9C=D0=B0=D1=80= =D0=BA wrote: > void scsi_req_complete(SCSIRequest *req) > { > assert(req->status !=3D -1); > req->bus->complete(req->bus, SCSI_REASON_DONE, > req->tag, > req->status); > } >=20 > (gdb) bt 1 > #0 0x0852cd88 in ?? () > (More stack frames follow...) > (gdb) frame 1 > #1 0x080f0f16 in scsi_command_complete (r=3D0x86252d8, status=3D, sense=3D) > at /home/mmarkk/src/KVM/qemu-kvm-0.12.3+noroms/hw/scsi-disk.c:105 > 105 scsi_req_complete(&r->req); > (gdb) print r->req->bus->complete > $7 =3D (scsi_completionfn) 0x852cd88 > (gdb) disassemble 0x852cd88 > No function contains specified address. >=20 >=20 > Corrupted memory ? >=20 Maybe. We fixed (hopefully) a few SCSI issues that showed up after guest reset. Those triggered "scsi-disk: Tag 0x0 already in use" as well. Does your scenario also include such a step, e.g. to boot into the installed kernel? In any case, could you retest with latest qemu-kvm from git? Thanks, Jan --=20 Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux