From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 196685] System becomes unresponsive after intel_iommu kernel error
Date: Thu, 17 Aug 2017 05:13:58 +0000 [thread overview]
Message-ID: <bug-196685-28872-dwtgwyDssk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196685-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196685
changbin.du@hotmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |changbin.du@hotmail.com
--- Comment #5 from changbin.du@hotmail.com ---
(In reply to Jason Hicks from comment #0)
> Created attachment 257969 [details]
> Kernel error in /var/log/kern.log
>
> I using a qemu virtual machine with VGA pass through. I have two Intel NICs
> in use by my motherboard, and I am passing through one of them so I can
> network with the VM over gigabit ethernet. I have been using this without
> issues for several months, but recently my system started becoming unstable.
> Before each crash, the network connection would abruptly end, and I suspect
> that is related to this. My desktop environment locks up, and after logging
> into my user account in another terminal, it is flooded with UFW block
> messages and no commands using sudo return anything. A kernel error
> appearing to be caused by intel_iommu is left in the kernel log. After this
> has happened yesterday, I ran memtest86 and my memory is okay. I am using an
> engineering sample CPU that is a down-clocked Intel E5 2680 v4. I haven't
> had any issues with this chip except recently when using VT-d.
Checking your dmesg, there are several kernel oops from different modules. Can
you share a full dmesg start from boot, to get the original error?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-08-17 5:14 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 [this message]
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
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-dwtgwyDssk@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