From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@kernel.org
Subject: [Bug 194837] VM with virtio-scsi drive often crashes during boot with kernel 4.11rc1
Date: Fri, 17 Mar 2017 19:02:59 +0000 [thread overview]
Message-ID: <bug-194837-11613-3vP3WkSW3v@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194837-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194837
--- Comment #15 from Thorsten Leemhuis (regressions@leemhuis.info) ---
Adam or somebody else: Can you please close this Bug to avoid confusion? There
clearly were some bugs in virtio_scsi, but those were already fixed.
But there are more bugs (at least for me): I bisectected the problem I'm still
seeing with todays mainline and found that "virtio_pci: use shared interrupts
for virtqueues" (5c34d002dcc7; from hch and mst) was the first bad commit for
me. Filed Bug 194911 to track that.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2017-03-17 19:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 23:53 [Bug 194837] New: VM with virtio-scsi drive often crashes during boot with kernel 4.11rc1 bugzilla-daemon
2017-03-09 23:58 ` [Bug 194837] " bugzilla-daemon
2017-03-09 23:59 ` bugzilla-daemon
2017-03-09 23:59 ` bugzilla-daemon
2017-03-10 0:47 ` bugzilla-daemon
2017-03-13 15:04 ` bugzilla-daemon
2017-03-13 15:15 ` bugzilla-daemon
2017-03-13 16:01 ` bugzilla-daemon
2017-03-14 19:25 ` bugzilla-daemon
2017-03-14 21:23 ` bugzilla-daemon
2017-03-14 22:56 ` bugzilla-daemon
2017-03-15 6:57 ` bugzilla-daemon
2017-03-15 7:02 ` bugzilla-daemon
2017-03-15 7:07 ` bugzilla-daemon
2017-03-15 7:47 ` bugzilla-daemon
2017-03-16 12:49 ` bugzilla-daemon
2017-03-16 16:18 ` bugzilla-daemon
2017-03-17 19:02 ` bugzilla-daemon [this message]
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=bug-194837-11613-3vP3WkSW3v@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@kernel.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.