All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Borislav Petkov <bp@alien8.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Christian König" <christian.koenig@amd.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Jiang Liu" <jiang.liu@linux.intel.com>
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
Date: Wed, 30 Sep 2015 20:07:27 +0200	[thread overview]
Message-ID: <20150930180727.GW3036@8bytes.org> (raw)
In-Reply-To: <20150930173619.GA3826@pd.tnic>

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
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 König" <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
Date: Wed, 30 Sep 2015 20:07:27 +0200	[thread overview]
Message-ID: <20150930180727.GW3036@8bytes.org> (raw)
In-Reply-To: <20150930173619.GA3826@pd.tnic>

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


  reply	other threads:[~2015-09-30 18:07 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 13:31 WARNING: CPU: 4 PID: 863 at include/drm/drm_crtc.h:1577 drm_helper_choose_encoder_dpms+0x88/0x90() Borislav Petkov
2015-09-22 19:06 ` Borislav Petkov
2015-09-22 19:06   ` Borislav Petkov
2015-09-22 19:58 ` Alex Deucher
2015-09-22 19:58   ` Alex Deucher
2015-09-22 20:21   ` Borislav Petkov
2015-09-22 20:21     ` Borislav Petkov
2015-09-22 20:54     ` Alex Deucher
2015-09-22 20:54       ` Alex Deucher
2015-09-23  7:25       ` Daniel Vetter
2015-09-23  8:59         ` Borislav Petkov
2015-09-23  8:59           ` Borislav Petkov
2015-09-23 14:44           ` Daniel Vetter
2015-09-23 14:44             ` Daniel Vetter
2015-09-23 16:06             ` Borislav Petkov
2015-09-23 16:06               ` Borislav Petkov
2015-09-23 16:18               ` Borislav Petkov
2015-09-23 16:18                 ` Borislav Petkov
2015-09-26 16:46                 ` WARNING: CPU: 4 PID: 863 at include/drm/drm_crtc.h:1577 drm_helper_choose_encoder_dpms+0x88/0x90() - evildoer found and neutralized Borislav Petkov
2015-09-26 16:46                   ` Borislav Petkov
2015-09-29  8:50                   ` Jiang Liu
2015-09-29 10:51                     ` Borislav Petkov
2015-09-29 10:51                       ` Borislav Petkov
2015-09-30  7:45                       ` Jiang Liu
2015-09-30  7:45                         ` Jiang Liu
2015-09-30 12:44                         ` Joerg Roedel
2015-09-30 17:00                           ` Jiang Liu
2015-09-30 17:36                             ` Borislav Petkov
2015-09-30 17:36                               ` Borislav Petkov
2015-09-30 18:07                               ` Joerg Roedel [this message]
2015-09-30 18:07                                 ` Joerg Roedel
2015-10-03  7:36                               ` Jiang Liu
2015-10-03  7:36                                 ` Jiang Liu
2015-10-03  9:35                                 ` Borislav Petkov
2015-10-03  9:35                                   ` Borislav Petkov
2015-10-05 10:03                                 ` Joerg Roedel
2015-10-05 10:03                                   ` Joerg Roedel
2015-10-06 13:13                                   ` Jiang Liu
2015-10-09 10:24                                     ` Joerg Roedel
2015-10-09 10:24                                       ` Joerg Roedel
2015-09-30 18:06                             ` Joerg Roedel
2015-09-30 18:06                               ` Joerg Roedel

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=20150930180727.GW3036@8bytes.org \
    --to=joro@8bytes.org \
    --cc=alexander.deucher@amd.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jiang.liu@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.