From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 191701] New: AMD-Vi completion-wait loop time outs freeze
system
Date: Mon, 02 Jan 2017 07:13:22 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.29.136]:58100 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1750808AbdABHN2 (ORCPT );
Mon, 2 Jan 2017 02:13:28 -0500
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 3A7432044C
for ; Mon, 2 Jan 2017 07:13:26 +0000 (UTC)
Received: from bugzilla2.web.kernel.org (bugzilla2.web.kernel.org [172.20.200.52])
by mail.kernel.org (Postfix) with ESMTP id C32432045B
for ; Mon, 2 Jan 2017 07:13:23 +0000 (UTC)
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=191701
Bug ID: 191701
Summary: AMD-Vi completion-wait loop time outs freeze system
Product: Virtualization
Version: unspecified
Kernel Version: 4.8.15
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: twtduck.ii@gmail.com
Regression: No
Created attachment 249591
--> https://bugzilla.kernel.org/attachment.cgi?id=249591&action=edit
The last few lines from the system log before I had to force reboot.
When I boot my 4.8.15 kernel, by the time my login screen shows, the system
rapidly lags out and freezes in a couple seconds. In the system log (relevant
subsection attached), this seems to be caused by AMD-Vi having time-outs.
Perhaps part of the problem is that the hardware that I'm using (Acer e5-553g)
has basically no virtualization support. I'd really like to upgrade my kernel
to fix some minor issues with my graphics driver, but this seems to be holding
me back and I don't know how to fix it. Since this wasn't a problem in 4.4.39,
I figured it might be a good idea to file a bug report, so that other people
with similar issues may have them resolved before trying to dig deep into the
heart of the problem and/or giving up.
There seems to have been a similar bug back in 3.6.11, that was more
widespread. After some searching, I haven't found this bug reported yet, so I
figured I'd go ahead and blaze that trail.
--
You are receiving this mail because:
You are watching the assignee of the bug.