From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 697510 <697510@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 697510] [NEW] Machine shut off after tons of lsi_scsi: error: MSG IN data too long
Date: Thu, 6 Jan 2011 09:43:45 +0000 [thread overview]
Message-ID: <AANLkTimmZH_bfXoSTxAg-cmuV+8O=ZNBJp36_ApJGRPe@mail.gmail.com> (raw)
In-Reply-To: <20110105050549.989.70900.malonedeb@wampee.canonical.com>
On Wed, Jan 5, 2011 at 5:05 AM, TiCPU <jeromepoulin@gmail.com> wrote:
> Using Virtio and Red Hat driver I get a STOP screen 0x100000d1 and machine either reboot, stay frozen or shut off.
Here the minidump would be useful and we should get in touch with the
person that maintains the virtio-blk Windows driver.
> Using SCSI the machine shuts off and I get tons of message on stdout;
[...]
> lsi_scsi: error: Unimplemented message 0x00
> (x8)
>
> lsi_scsi: error: MSG IN data too long
> lsi_scsi: error: Unimplemented message 0x00
> (x760)
>
> lsi_scsi: error: MSG IN data too long
> lsi_scsi: error: MSG IN data too long
> kvm: /build/buildd/qemu-kvm-0.12.5+noroms/hw/lsi53c895a.c:512: lsi_do_dma: Assertion `s->current' failed.
Looks like the LSI SCSI device emulation is getting out of sync with
the guest's device driver.
Can you give more details or a test case that reproduces these
problems? Which backup software are you using and is it known to do
special purpose SCSI commands?
Stefan
next prev parent reply other threads:[~2011-01-06 9:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 5:05 [Qemu-devel] [Bug 697510] [NEW] Machine shut off after tons of lsi_scsi: error: MSG IN data too long TiCPU
2011-01-06 9:43 ` Stefan Hajnoczi [this message]
2011-01-06 13:13 ` Stefan Hajnoczi
2011-01-27 20:46 ` [Qemu-devel] [Bug 697510] " vrozenfe
2011-01-27 21:20 ` TiCPU
2011-01-27 22:57 ` vrozenfe
2016-12-19 18:27 ` Thomas Huth
2017-02-18 4:17 ` Launchpad Bug Tracker
2020-06-16 15:47 ` Bugs SysSec
2020-06-16 15:55 ` Bugs SysSec
2020-07-10 22:22 ` Alexander Bulekov
2021-05-03 9:28 ` Thomas Huth
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='AANLkTimmZH_bfXoSTxAg-cmuV+8O=ZNBJp36_ApJGRPe@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=697510@bugs.launchpad.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).