Skip to content
Snippets Groups Projects

Screen doesn't update unless the mouse is being moved

    • Closed Issue created by Mike Lothian @FireBurn

    I don't see this issue in Linus's tree 5.8-rc4, I do see it in both airlied's drm-next and agd5f's drm-next branch

    System devices:

    00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #6 (rev f1)
00:1c.6 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #7 (rev f1)
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation HM170 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Amethyst XT [Radeon R9 M295X]
3b:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
3c:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
3d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 (rev 01)

    I've bisected this issue to:

    commit 0a19b068acc47d05212f03e494381926dc0381e2 (HEAD, refs/bisect/bad)
Merge: 48778464bb7d 114427b8927a
Author: Dave Airlie <airlied@redhat.com>
Date:   Tue Jun 23 10:58:28 2020 +1000

    Merge tag 'drm-misc-next-2020-06-19' of git://anongit.freedesktop.org/drm/drm-misc into drm-next
    
    drm-misc-next for v5.9:

    The only thing of notice in the dmesg when running a broken kernel is:

    Jul 06 16:28:53 axion kernel: DMAR: DRHD: handling fault status reg 3
Jul 06 16:28:53 axion kernel: DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr 3a600000 [fault reason 06] PTE Read access is not set
Jul 06 16:28:53 axion kernel: DMAR: Intel(R) Virtualization Technology for Directed I/O
Jul 06 16:28:53 axion kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 06 16:28:53 axion kernel: software IO TLB: mapped [mem 0x2b903000-0x2f903000] (64MB)
Jul 06 16:28:53 axion kernel: DMAR: DRHD: handling fault status reg 3
Jul 06 16:28:53 axion kernel: DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr 3a600000 [fault reason 06] PTE Read access is not set
Jul 06 16:28:53 axion kernel: DMAR: DRHD: handling fault status reg 3
Jul 06 16:28:53 axion kernel: DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr 3a626000 [fault reason 06] PTE Read access is not set
Jul 06 16:28:53 axion kernel: DMAR: DRHD: handling fault status reg 3

    [Note these warnings are when DMAR is initialised, before i915.ko is loaded]

    dmesg.broken.txt dmesg.working.txt

    Edited
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

      • Mike Lothian
        Mike Lothian @FireBurn ·
        Author

        I also see huge spikes in cpu usage with kwin_wayland ~450%

      • Chris Wilson
        Chris Wilson @ickle ·
        Reporter

        Does kwin produce any logs that might explain the abnormal CPU usage? Otherwise a perf/sysprof snapshot to see where the time goes. It's either going to be hotplug/modesetting or swrast. Probably.

      • Mike Lothian
        Mike Lothian @FireBurn ·
        Author

        I've not seen anything obvious in any of the logs

      • Mike Lothian
        Mike Lothian @FireBurn ·
        Author

        As git found the merge point, can you suggest a way I can find the specific patch from that merge and I'll try bisecting again

      • Chris Wilson
        Chris Wilson @ickle ·
        Reporter

        Git's sensible enough to descend into a merge, it will check both parents to find the buggy branch to take. If you have patience, repeat the bisect, as the merge commit itself although it contains conflict resolutions doesn't look suspicious.

        You might try bisecting the DMAR errors if they are stable. They may caused by the system being left in a bad state following the bug [but that suggests the error will be visible on the warm reboot after the bug is hit, so be careful if bisecting those.] Or it may just be the DMAR setup was broken. Or it may be the uefi/efifb upset. A read error would suggest the display is trying to read from the void.

      • Mike Lothian
        Mike Lothian @FireBurn ·
        Author

        Right I'm going manually to 114427b8927a4def2942b2b886f7e4aeae289ccb to confirm if it's broken and bisect between there and 5.7.0-rc1

      • Please register or sign in to reply
    • Chris Wilson changed the description

      changed the description

    • Mike Lothian
      Mike Lothian @FireBurn ·
      Author

      So, it seems the issue I'm seeing was in 5.8-rc2, and fixed before 5.8-rc4, I'm bisecting to see what fixed it

    • Mike Lothian
      Mike Lothian @FireBurn ·
      Author

      So the real fix was:

      48f0bcfb7aad2c6eb4c1e66476b58475aa14393e is the first fixed commit
commit 48f0bcfb7aad2c6eb4c1e66476b58475aa14393e
Author: Lu Baolu <baolu.lu@linux.intel.com>
Date:   Tue Jun 23 07:13:45 2020 +0800

    iommu/vt-d: Fix misuse of iommu_domain_identity_map()
    
    The iommu_domain_identity_map() helper takes start/end PFN as arguments.
    Fix a misuse case where the start and end addresses are passed.
    
    Fixes: e70b081c6f376 ("iommu/vt-d: Remove IOVA handling code from the non-dma_ops path")
    Reported-by: Alex Williamson <alex.williamson@redhat.com>
    Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
    Reviewed-by: Jerry Snitselaar <jsnitsel@redhat.com>
    Cc: Tom Murphy <murphyt7@tcd.ie>
    Link: https://lore.kernel.org/r/20200622231345.29722-7-baolu.lu@linux.intel.com
    Signed-off-by: Joerg Roedel <jroedel@suse.de>

 drivers/iommu/intel/iommu.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
    • Chris Wilson
      Chris Wilson @ickle ·
      Reporter

      Thanks!

    • Chris Wilson closed

      closed

    Please register or sign in to reply