From: Lu Baolu <baolu.lu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Dmitrii Tcvetkov <demfloro-dmrBKrQMA3sox3rIn2DAYQ@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: No video output on 4.19-rc1 on Dell XPS 13 9360
Date: Sun, 9 Sep 2018 10:01:17 +0800 [thread overview]
Message-ID: <89dff474-7baa-83ce-d70d-fffc4699d3ce@linux.intel.com> (raw)
In-Reply-To: <20180908165747.16c2843c-STI+9kRLTpF82hYKe6nXyg@public.gmane.org>
Hi,
The fix has been posted here.
https://lkml.org/lkml/2018/9/8/14
Best regards,
Lu Baolu
On 09/08/2018 09:57 PM, Dmitrii Tcvetkov wrote:
> I've sent the email[1] before to iommu and lkml mailing lists only, but
> according to iommu mailing list archive it wasn't received[2]. I'm
> resending it to Lu Baolu and Joerg Roedel with proper kernel .config
> file. Sorry if the duplication is unnecessary.
>
> Since 4.19-rc1 my laptop boots with vertical static set of rows of dots
> on the screen instead of proper video output. SSH'ing into it allowed
> to get dmesg-without-pt.log output, PCI device 00:02.0 is VGA
> compatible controller: Intel Corporation HD Graphics 620 (rev 02)
>
> Appending "iommu=pt" to kernel cmdline allowed to boot with functional
> graphics, but gave dmesg-with-pt.log output.
>
> Bisect between v4.18 and v4.19-rc1 tags led me to commit
> a7fc93fed94b173e2 (iommu/vt-d: Allocate and free pasid table).
>
> Reverting this commit allows to build kernel on current master
> (a12ed06ba2d3fa60e), which boots with functional graphical output
> without specifying "iommu=pt".
> Dmesg output is in dmesg-with-revert.log.
>
> Without the revert current master boots like 4.19-rc1.
>
> [1] https://lkml.org/lkml/2018/9/7/1081
> [2] https://lists.linuxfoundation.org/pipermail/iommu/2018-September/date.html
>
WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Dmitrii Tcvetkov <demfloro@demfloro.ru>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: No video output on 4.19-rc1 on Dell XPS 13 9360
Date: Sun, 9 Sep 2018 10:01:17 +0800 [thread overview]
Message-ID: <89dff474-7baa-83ce-d70d-fffc4699d3ce@linux.intel.com> (raw)
In-Reply-To: <20180908165747.16c2843c@fire.localdomain>
Hi,
The fix has been posted here.
https://lkml.org/lkml/2018/9/8/14
Best regards,
Lu Baolu
On 09/08/2018 09:57 PM, Dmitrii Tcvetkov wrote:
> I've sent the email[1] before to iommu and lkml mailing lists only, but
> according to iommu mailing list archive it wasn't received[2]. I'm
> resending it to Lu Baolu and Joerg Roedel with proper kernel .config
> file. Sorry if the duplication is unnecessary.
>
> Since 4.19-rc1 my laptop boots with vertical static set of rows of dots
> on the screen instead of proper video output. SSH'ing into it allowed
> to get dmesg-without-pt.log output, PCI device 00:02.0 is VGA
> compatible controller: Intel Corporation HD Graphics 620 (rev 02)
>
> Appending "iommu=pt" to kernel cmdline allowed to boot with functional
> graphics, but gave dmesg-with-pt.log output.
>
> Bisect between v4.18 and v4.19-rc1 tags led me to commit
> a7fc93fed94b173e2 (iommu/vt-d: Allocate and free pasid table).
>
> Reverting this commit allows to build kernel on current master
> (a12ed06ba2d3fa60e), which boots with functional graphical output
> without specifying "iommu=pt".
> Dmesg output is in dmesg-with-revert.log.
>
> Without the revert current master boots like 4.19-rc1.
>
> [1] https://lkml.org/lkml/2018/9/7/1081
> [2] https://lists.linuxfoundation.org/pipermail/iommu/2018-September/date.html
>
next prev parent reply other threads:[~2018-09-09 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 13:57 No video output on 4.19-rc1 on Dell XPS 13 9360 Dmitrii Tcvetkov
[not found] ` <20180908165747.16c2843c-STI+9kRLTpF82hYKe6nXyg@public.gmane.org>
2018-09-09 2:01 ` Lu Baolu [this message]
2018-09-09 2:01 ` Lu Baolu
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=89dff474-7baa-83ce-d70d-fffc4699d3ce@linux.intel.com \
--to=baolu.lu-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=demfloro-dmrBKrQMA3sox3rIn2DAYQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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 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.