From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932947AbbI3SHb (ORCPT <rfc822;w@1wt.eu>);
	Wed, 30 Sep 2015 14:07:31 -0400
Received: from 8bytes.org ([81.169.241.247]:42902 "EHLO theia.8bytes.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S932190AbbI3SH3 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 30 Sep 2015 14:07:29 -0400
Date: Wed, 30 Sep 2015 20:07:27 +0200
From: Joerg Roedel <joro@8bytes.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Jiang Liu <jiang.liu@linux.intel.com>, Daniel Vetter <daniel@ffwll.ch>,
        Thomas Gleixner <tglx@linutronix.de>,
        Bjorn Helgaas <bhelgaas@google.com>,
        Alex Deucher <alexdeucher@gmail.com>,
        Alex Deucher <alexander.deucher@amd.com>,
        Christian =?iso-8859-1?Q?K=F6nig?= <christian.koenig@amd.com>,
        Maling list - DRI developers 
	<dri-devel@lists.freedesktop.org>,
        lkml <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: CPU: 4 PID: 863 at include/drm/drm_crtc.h:1577
 drm_helper_choose_encoder_dpms+0x88/0x90() - evildoer found and neutralized
Message-ID: <20150930180727.GW3036@8bytes.org>
References: <20150923144450.GD3383@phenom.ffwll.local>
 <20150923160621.GA3446@pd.tnic>
 <20150923161839.GB3446@pd.tnic>
 <20150926164651.GA3640@pd.tnic>
 <560A50DC.1040505@linux.intel.com>
 <20150929105138.GA12037@nazgul.tnic>
 <560B9323.6000309@linux.intel.com>
 <20150930124432.GS3036@8bytes.org>
 <560C153C.10600@linux.intel.com>
 <20150930173619.GA3826@pd.tnic>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150930173619.GA3826@pd.tnic>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Sep 30, 2015 at 07:36:19PM +0200, Borislav Petkov wrote:
> Right, so this fixes the issue on my box, courtesy of Joerg. WE
> basically don't disable the IRQ on MSI-enabled devices. The AMD IOMMU
> uses a barebones PCI device but not a PCI driver, which would be an
> overkill.

Well, not only overkill, but actually harmful. As I just wrote to
Jiang, a device can be forcibly unbound from its driver, which is
something we don't want for the IOMMU.


	Joerg