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: Tue, 22 Aug 2017 07:47:21 +0000
Message-ID: <bug-196685-28872-6KzkHGkthv@https.bugzilla.kernel.org/>
References: <bug-196685-28872@https.bugzilla.kernel.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
To: kvm@kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:46136 "EHLO
        mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1754687AbdHVHrX (ORCPT
        <rfc822;kvm@vger.kernel.org>); Tue, 22 Aug 2017 03:47:23 -0400
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
        by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 126E02881A
        for <kvm@vger.kernel.org>; Tue, 22 Aug 2017 07:47:23 +0000 (UTC)
In-Reply-To: <bug-196685-28872@https.bugzilla.kernel.org/>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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

--- Comment #15 from changbin.du@hotmail.com ---
(In reply to Jeff Cook from comment #13)
> For the record. I have been running "Linux kvm_master
> 4.13.0-rc5-g58d4e450a490 #1 SMP PREEMPT", a git build from a commit made on
> Friday (8/19/2017), for the last 36 hours or so. On this commit, it appears
> that I received the warning message discussed here, but nothing crashed and
> the system continues to function in what appears to be a normal manner.
> 
> I will attach full dmesg for reference. If this is indeed the same condition
> and the trap is successful, the crasher may have been fixed somewhere in the
> 4.13 cycle.

The oops has been fixed by https://py3.patchwork.dja.id.au/patch/41163/. This
patch should be backported to stable branches.

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