From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 196685] System becomes unresponsive after intel_iommu kernel error
Date: Sun, 20 Aug 2017 13:03:41 +0000 [thread overview]
Message-ID: <bug-196685-28872-hPbciRjHtS@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 #12 from Jason Hicks (jaszhix@gmail.com) ---
Created attachment 258029
--> https://bugzilla.kernel.org/attachment.cgi?id=258029&action=edit
dmesg aug 18-aug 20
This is an updated dmesg log from boot to kernel oops errors. This shows the
system being on for a couple days with the VM running with no issues, but
finally when left on over night, and then using the VM this morning (August
20), it flooded the log with call stacks for a while before my computer
completely froze. In addition, hardware differences between this and my last
complete dmesg log include removed USB devices - a 8GB usb drive, and a Sony
controller was removed.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-08-20 13:04 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 [this message]
2017-08-20 14:23 ` bugzilla-daemon
2017-08-21 5:42 ` bugzilla-daemon
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-hPbciRjHtS@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