From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 196685] System becomes unresponsive after intel_iommu kernel
error
Date: Sun, 20 Aug 2017 13:03:41 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
To: kvm@kernel.org
Return-path:
Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:59468 "EHLO
mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK)
by vger.kernel.org with ESMTP id S1752856AbdHTNEO (ORCPT
); Sun, 20 Aug 2017 09:04:14 -0400
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
by mail.wl.linuxfoundation.org (Postfix) with ESMTP id B2E12285E6
for ; Sun, 20 Aug 2017 13:04:13 +0000 (UTC)
In-Reply-To:
Sender: kvm-owner@vger.kernel.org
List-ID:
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.