From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 191701] New: AMD-Vi completion-wait loop time outs freeze system
Date: Mon, 02 Jan 2017 07:13:22 +0000 [thread overview]
Message-ID: <bug-191701-28872@https.bugzilla.kernel.org/> (raw)
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.
reply other threads:[~2017-01-02 7:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-191701-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.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.