From: Lu Baolu <baolu.lu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org,
"joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org"
<joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Borken IOMMU+i915
Date: Mon, 16 Jul 2018 09:21:21 +0800 [thread overview]
Message-ID: <5B4BF311.5020500@linux.intel.com> (raw)
In-Reply-To: <84fu0kaomw.wl-Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org>
Hi Peter,
There is already a patch to revert that broken patch.
https://patchwork.kernel.org/patch/10513017/
Best regards,
Lu Baolu
On 07/15/2018 04:29 PM, Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org wrote:
> Hi Lu,
> In recent kernels, i915 graphics with intel_iommu=on has been
> giving me a blank screen.
>
> git bisect points at your patch ab96746aaa34
> "iommu/vt-d: Clean up pasid quirk for pre-production devices"
>
> Either one of the pre-production devices made it into my Dell
> laptop, or there's something else wrong with the patch.
>
> Reverting that patch gives me text console and X11 graphics;
> keeping it in yields a blank screen on boot.
>
> My laptop is a Dell Inc. Precision 7710/0PMJX2, BIOS 1.15.4 12/08/2017
> CPU is Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz
> (family: 0x6, model: 0x5e, stepping: 0x3)
>
> Peter C
prev parent reply other threads:[~2018-07-16 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 8:29 Borken IOMMU+i915 Peter.Chubb-RgbkMxAV74wUb6iz2VnApA
[not found] ` <84fu0kaomw.wl-Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org>
2018-07-16 1:21 ` Lu Baolu [this message]
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=5B4BF311.5020500@linux.intel.com \
--to=baolu.lu-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).