All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: socketpair@gmail.com
Cc: qemu-devel@nongnu.org, Bug 595438 <595438@bugs.launchpad.net>
Subject: [Qemu-devel] Re: [Bug 595438] Re: KVM segmentation fault, using SCSI+writeback and linux 2.4 guest
Date: Fri, 02 Jul 2010 18:28:59 +0200	[thread overview]
Message-ID: <4C2E13CB.2020009@siemens.com> (raw)
In-Reply-To: <20100702100920.24319.7675.malone@palladium.canonical.com>

Коренберг Марк wrote:
> void scsi_req_complete(SCSIRequest *req)
> {
>     assert(req->status != -1);
>     req->bus->complete(req->bus, SCSI_REASON_DONE,
>                        req->tag,
>                        req->status);
> }
> 
> (gdb) bt 1
> #0  0x0852cd88 in ?? ()
> (More stack frames follow...)
> (gdb) frame 1
> #1  0x080f0f16 in scsi_command_complete (r=0x86252d8, status=<value optimized out>, sense=<value optimized out>)
>     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 = (scsi_completionfn) 0x852cd88
> (gdb) disassemble 0x852cd88
> No function contains specified address.
> 
> 
> Corrupted memory ?
> 

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

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-07-02 16:29 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  9:52 [Qemu-devel] [Bug 595438] [NEW] segmentation scsi writeback Коренберг Марк
2010-06-17  9:53 ` [Qemu-devel] [Bug 595438] " Коренберг Марк
2010-06-17  9:57 ` Коренберг Марк
2010-06-17 10:05 ` [Qemu-devel] [Bug 595438] Re: KVM segmentation fault, using SCSI+writeback and linux 2.4 guest Коренберг Марк
2010-06-18  5:29 ` Коренберг Марк
2010-07-01  6:13 ` Jes Sorensen
2010-07-02  6:57 ` Коренберг Марк
2010-07-02  6:58 ` Коренберг Марк
2010-07-02  7:12 ` Коренберг Марк
2010-07-02  7:24 ` Коренберг Марк
2010-07-02  9:38 ` Коренберг Марк
2010-07-02  9:40 ` Коренберг Марк
2010-07-02 10:09 ` Коренберг Марк
2010-07-02 16:28   ` Jan Kiszka [this message]
2010-07-10  9:18 ` Коренберг Марк
2010-07-10  9:19 ` Коренберг Марк
2010-07-10 10:32   ` [Qemu-devel] " Jan Kiszka
2010-07-10  9:27 ` [Qemu-devel] " Коренберг Марк
2010-07-10  9:41 ` Коренберг Марк
2010-07-12  8:58 ` Коренберг Марк
2010-07-13  6:18 ` Коренберг Марк
2010-07-15  7:27 ` Коренберг Марк
2010-07-15 11:05   ` [Qemu-devel] " Jan Kiszka
2010-07-28 12:23 ` [Qemu-devel] " Коренберг Марк
2010-07-28 12:29 ` Коренберг Марк
2010-07-28 14:35 ` Serge Hallyn
2010-07-28 21:07   ` [Qemu-devel] " Serge Hallyn
2010-07-29 13:26 ` [Qemu-devel] " Коренберг Марк
2010-07-29 14:05   ` [Qemu-devel] " Serge Hallyn
2010-07-31  8:01 ` [Qemu-devel] " Коренберг Марк
2010-08-10  3:15 ` Serge Hallyn
2010-08-10  3:28 ` Serge Hallyn
2010-08-10  4:40 ` Steve Beattie
2010-08-17  6:30 ` Martin Pitt
2010-08-23  9:47 ` Thierry Carrez
2010-08-23 11:30 ` Thierry Carrez
2010-08-25  7:19 ` Martin Pitt
2010-08-25  8:18 ` Launchpad Bug Tracker
2010-10-07 14:00 ` Jean-Baptiste Lallement
2010-11-11 23:00 ` Michael Tokarev
2010-11-12  0:03 ` Bug Watch Updater
2010-11-13  0:34 ` Bug Watch Updater
2010-11-18  3:50 ` Serge Hallyn
2010-11-18  4:50 ` Коренберг Марк
2010-11-22 15:13 ` Serge Hallyn
2010-12-01  3:39 ` Serge Hallyn
2010-12-01  6:33   ` [Qemu-devel] " Dustin Kirkland
2010-12-02  1:59 ` [Qemu-devel] " Imre Gergely
2010-12-02 12:00 ` Imre Gergely
2010-12-02 14:46 ` Martin Pitt
2010-12-03 15:27 ` Launchpad Bug Tracker
2011-02-20 17:17 ` Aurelien Jarno
2011-07-29  1:34 ` Serge Hallyn

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=4C2E13CB.2020009@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=595438@bugs.launchpad.net \
    --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 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.