From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 194883] kvm: workqueue lockup
Date: Mon, 27 Mar 2017 15:45:29 +0000 [thread overview]
Message-ID: <bug-194883-28872-JymDtYtmbK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194883-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194883
Thorsten Leemhuis (regressions@leemhuis.info) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |regressions@leemhuis.info
--- Comment #1 from Thorsten Leemhuis (regressions@leemhuis.info) ---
Does this problem still show up in rc4? And did everything work fine with 4.10?
JFYI: I added this report to the list of regressions for Linux 4.11.
I'll watch this place for further updates on this issue to document
progress in my weekly reports, hence to allow me to keep track please send a
quick note here in case this issue gets discussed somewhere else.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2017-03-27 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 18:24 [Bug 194883] New: kvm: workqueue lockup bugzilla-daemon
2017-03-27 15:45 ` 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-194883-28872-JymDtYtmbK@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox