From: Jiang Liu <jiang.liu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: "Borislav Petkov" <bp@alien8.de>,
"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: Tue, 6 Oct 2015 21:13:11 +0800 [thread overview]
Message-ID: <5613C8E7.8000308@linux.intel.com> (raw)
In-Reply-To: <20151005100354.GB12506@8bytes.org>
On 2015/10/5 18:03, Joerg Roedel wrote:
> Hi Jiang,
>
> On Sat, Oct 03, 2015 at 03:36:35PM +0800, Jiang Liu wrote:
>> So to summary, I think we only need following change to fix the
>> regression:
>> int pcibios_alloc_irq(struct pci_dev *dev)
>> {
>> + if (pci_dev_msi_enabled(dev))
>> + return -EBUSY;
>>
>> What do you think?
>
> Yes, that works too and has the added benefit that no driver can attach
> to the iommu device and get in the way of the driver.
>
> Will you send the patch for this change or should I do it?
Hi Joerg,
We are on leave for Chinese National Holiday and has limited
access to my working environment. It would be appreciated if you could
help to send out a patch for it. Otherwise I will send out a patch
within 2-3 days.
Thanks!
Gerry
next prev parent reply other threads:[~2015-10-06 13:13 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
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 [this message]
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=5613C8E7.8000308@linux.intel.com \
--to=jiang.liu@linux.intel.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=joro@8bytes.org \
--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.