From: Gerd Hoffmann <kraxel@redhat.com>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: Kevin Wolf <kwolf@redhat.com>,
hdegoede@redhat.com,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] usb-storage assertions
Date: Mon, 18 Jan 2016 10:38:43 +0100 [thread overview]
Message-ID: <1453109923.23289.4.camel@redhat.com> (raw)
In-Reply-To: <CABYiri9SyUf4OuPijAPo7krjy0QfTAXPBJOkcYEk-JDMSWLGUg@mail.gmail.com>
On Fr, 2016-01-15 at 21:08 +0300, Andrey Korolyov wrote:
> Just checked, Linux usb driver decided to lose a disk during a
> 'stress-test' over unpacking linux source instead of triggering an
> assertion in 2.5 (and to irreparably damage its ext4 as well),
Ok, so behavior changed here from 2.2 -> 2.5. I don't see disk
corruption in my tests, but linux guest resets the usb-storage device
now and then. Seems to be able to resume operations though, there are
no disk errors in the logs.
> NetBSD
> 7.0 reboot action hangs on USB_RESET and NetBSD 5.1 triggers second of
> mentioned asserts. Backend itself is a regular USB2-SATA adapter with
> Intel S3500 SSD, hence it should not trigger first timing-related
> assertion at all.
ok. Had no trouble with freebsd, will go fetch netbsd images. What
arch is this? i386? x86_64?
cheers,
Gerd
next prev parent reply other threads:[~2016-01-18 9:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 17:34 [Qemu-devel] usb-storage assertions Andrey Korolyov
2016-01-12 14:17 ` Gerd Hoffmann
2016-01-12 14:36 ` Kevin Wolf
2016-01-12 14:56 ` Daniel P. Berrange
2016-01-13 16:13 ` Gerd Hoffmann
2016-01-13 16:28 ` Andrey Korolyov
2016-01-15 18:08 ` Andrey Korolyov
2016-01-18 9:38 ` Gerd Hoffmann [this message]
2016-01-18 9:50 ` Andrey Korolyov
2016-01-18 13:55 ` Gerd Hoffmann
2016-01-18 23:49 ` Andrey Korolyov
2016-01-19 7:13 ` Gerd Hoffmann
2016-01-19 10:59 ` Andrey Korolyov
2016-01-19 11:44 ` Gerd Hoffmann
2016-01-19 14:19 ` Gerd Hoffmann
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=1453109923.23289.4.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=andrey@xdel.ru \
--cc=hdegoede@redhat.com \
--cc=kwolf@redhat.com \
--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 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.