From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 196685] System becomes unresponsive after intel_iommu kernel error
Date: Mon, 21 Aug 2017 05:42:36 +0000 [thread overview]
Message-ID: <bug-196685-28872-U3IgaiJccD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196685-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196685
--- Comment #13 from Jeff Cook (jeff@jeffcook.io) ---
For the record. I have been running "Linux kvm_master 4.13.0-rc5-g58d4e450a490
#1 SMP PREEMPT", a git build from a commit made on Friday (8/19/2017), for the
last 36 hours or so. On this commit, it appears that I received the warning
message discussed here, but nothing crashed and the system continues to
function in what appears to be a normal manner.
I will attach full dmesg for reference. If this is indeed the same condition
and the trap is successful, the crasher may have been fixed somewhere in the
4.13 cycle.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-08-21 5:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 4:49 [Bug 196685] New: System becomes unresponsive after intel_iommu kernel error bugzilla-daemon
2017-08-17 4:50 ` [Bug 196685] " bugzilla-daemon
2017-08-17 4:52 ` bugzilla-daemon
2017-08-17 5:00 ` bugzilla-daemon
2017-08-17 5:02 ` bugzilla-daemon
2017-08-17 5:13 ` bugzilla-daemon
2017-08-17 5:27 ` bugzilla-daemon
2017-08-17 5:30 ` bugzilla-daemon
2017-08-18 10:14 ` bugzilla-daemon
2017-08-19 16:58 ` bugzilla-daemon
2017-08-19 17:03 ` bugzilla-daemon
2017-08-19 17:11 ` bugzilla-daemon
2017-08-20 13:03 ` bugzilla-daemon
2017-08-20 14:23 ` bugzilla-daemon
2017-08-21 5:42 ` bugzilla-daemon [this message]
2017-08-21 5:47 ` bugzilla-daemon
2017-08-22 7:47 ` bugzilla-daemon
2017-08-22 9:01 ` bugzilla-daemon
2017-08-22 15:00 ` bugzilla-daemon
2017-08-23 7:04 ` bugzilla-daemon
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-196685-28872-U3IgaiJccD@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 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.