public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 196685] System becomes unresponsive after intel_iommu kernel error
Date: Sat, 19 Aug 2017 16:58:34 +0000	[thread overview]
Message-ID: <bug-196685-28872-TWcZ19Oz9n@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196685-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=196685

Jeff Cook (jeff@jeffcook.io) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeff@jeffcook.io

--- Comment #9 from Jeff Cook (jeff@jeffcook.io) ---
I've been getting a very similar crash on 4.12.x, also making heavy use of PCI
passthrough. Came across this bug, as I've been searching regularly looking for
others encountering the same troubles.

A snippet of the log observed on 4.12.{3/5}:

kernel: BUG: unable to handle kernel paging request at ffffffffc0955f96
kernel: IP: report_bug+0x94/0x120
kernel: PGD a67a0c067 
kernel: P4D a67a0c067 
kernel: PUD a67a0e067 
kernel: PMD 495886067 
kernel: PTE 800000049bbdd161

Last night I experienced a hard lock with 4.11.9, which has heretofore been
stable. The system did not log any information about that crash. This may mean
that the issue existed prior to 4.12, but was just much harder to trigger.

See also my related bug report at https://bugs.archlinux.org/task/55141.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2017-08-19 16:58 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 [this message]
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-TWcZ19Oz9n@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