driver issueshttps://gitlab.freedesktop.org/groups/xorg/driver/-/issues2021-04-20T21:08:49Zhttps://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/36Invoking `xinput --disable [ || --enable] <device_xID>` kills X session2021-04-20T21:08:49ZCedric BhiheInvoking `xinput --disable [ || --enable] <device_xID>` kills X session_[Host info: Laptop Dell XPS15 running OS Arch x86_64 GNU/Linux 5.11.13-arch1-1 with gdm 40.0-1 on xorg-server 1.20.10-3]_
Whenever I invoke `$ xinput --disable <device_name>` xorg-server crashes and in so doing kills everything in the..._[Host info: Laptop Dell XPS15 running OS Arch x86_64 GNU/Linux 5.11.13-arch1-1 with gdm 40.0-1 on xorg-server 1.20.10-3]_
Whenever I invoke `$ xinput --disable <device_name>` xorg-server crashes and in so doing kills everything in the opened gdm session. The host recovers and presents USER with a new gdm session login dialog. Everything else seems completely normal on host.
The xorg-xinput version is 1.6.3-2, upgraded from 1.6.3-1 on 2020.05.19 (way before the issue appeared) <br>
On the other hand, gdm + the linux kernel and headers were upgraded recently (from /var/log/pacman.log):
- [2021-04-09T08:29:29] [ALPM] upgraded linux (5.11.11.arch1-1 -> >> 5.11.12.arch1-1)
- [2021-04-09T08:29:30] [ALPM] upgraded gdm (3.38.2.1-1 -> 40.0-1)
2021.04.09 is when the issue started to manifest itself. In the past 5 days I have seen at least 2 similar reports appear on that or very similar looking issues, essentially from archers, who as I, run X.
- http://paste.c-net.org/BunksTyped
- https://bbs.archlinux.org/viewtopic.php?id=264928
This issue is perfectly reproducible and is triggered by execution of the `xinput --disable <xID>` or `xinput --enable <xID>` commands, no matter what the `<xID>` is ...
The full systemd journal trace of the coredump is available in the attached file below where two X-crash events are recorded.
[journald_2021.04.14.log](/uploads/0cf4753bd8288a33a67285b831259e91/journald_2021.04.14.log)Peter HuttererPeter Huttererhttps://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194Display output laggy from iGPU when operating on desktop with attaching AMD R...2021-04-15T10:09:01ZJeremy SzuDisplay output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)[Steps to reproduce this issue]
1. Install a focal base image
2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)).
4. After loggi...[Steps to reproduce this issue]
1. Install a focal base image
2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)).
4. After logging it, the display shows laggy.
[Additional information]
1. doesn't see this issue if selecting 'Wayland'
2. add a config
```
Section "OutputClass"
Identifier "MyRadeon"
MatchDriver "radeon"
Driver "modesetting"
EndSection
```
to fallback to use modesetting could workaround this issue.
```
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
Uname: Linux 5.10.0-1019-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 9 16:23:42 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375]
Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Renoir [103c:872b]
InstallationDate: Installed on 2021-04-09 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2020
dmi.bios.release: 2.0
dmi.bios.vendor: HP
dmi.bios.version: S09 Ver. 02.02.00
dmi.board.name: 872B
dmi.board.vendor: HP
dmi.board.version: KBC Version 09.94.00
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 9.148
dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
dmi.product.family: 103C_53307F HP EliteDesk
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
```
[XorgLog.txt](/uploads/772d055ed0bde6de5690d95936dd0e0f/XorgLog.txt)https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/35gnome-shell | gnome-shell: libinput error: client bug: timer event3 debounce ...2021-09-03T02:12:09Z49studebakergnome-shell | gnome-shell: libinput error: client bug: timer event3 debounce short: offset negative (-0ms) (#2041)gnome-shell | gnome-shell: libinput error: client bug: timer event3 debounce short: offset negative (-0ms) (#2041)
Reported to:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2041#note_1050208
https://bugs.launchpad.net/ubuntu/+...gnome-shell | gnome-shell: libinput error: client bug: timer event3 debounce short: offset negative (-0ms) (#2041)
Reported to:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2041#note_1050208
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1856553https://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/-/issues/13synclient AreaLeftEdge=-1000 doesn't work2021-04-09T23:33:28ZPip Cetsynclient AreaLeftEdge=-1000 doesn't workI'm using this driver with Debian GNU/Linux on an Apple M1-based machine, which has a huge touchpad which I find impossible to work with unless I set both AreaRightEdge (to around 4000) and AreaLeftEdge; however, the default synclient.c ...I'm using this driver with Debian GNU/Linux on an Apple M1-based machine, which has a huge touchpad which I find impossible to work with unless I set both AreaRightEdge (to around 4000) and AreaLeftEdge; however, the default synclient.c source caps the AreaLeftEdge minimum at 0, so 1 is the lowest usable value, and that disables the entire half of that touchpad.
Will attach the obvious patch once I figure out how to do that in this GitLab.https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/34xorg-server segfault on this libinput plugin2021-04-16T02:15:30ZAlkaidxorg-server segfault on this libinput pluginDear maintainer,
When switching tty, xorg will segfault on this plugin. Stack trace is available in the attached [Xorg.0.log.old](/uploads/44d1059359295ebcb0d7df6b0cc88618/Xorg.0.log.old).
My environment: archlinux, gnome40.0, xorg-serv...Dear maintainer,
When switching tty, xorg will segfault on this plugin. Stack trace is available in the attached [Xorg.0.log.old](/uploads/44d1059359295ebcb0d7df6b0cc88618/Xorg.0.log.old).
My environment: archlinux, gnome40.0, xorg-server 1.20.10, xf86-input-libinput 1.0.0, kernel 5.11.11, nvidia 460.67.
The same problem has also been reported in [Ubuntu](https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1918985).
On my laptop, the segfault only happens when using the nvidia driver. No segfault when using with intel i915.
Using gdb, I pinpoint that the LibinputSetPropertyTapButtonmap does not check device against NULL (i.e. does not call `xf86libinput_check_device`) and returns `Success` at [this line](https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/blob/master/src/xf86libinput.c#L4526). Later, the `Success` lead to a NULL dereference at [this line](https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/blob/master/src/xf86libinput.c#L774).
Not sure when should this plugin check for device != NULL and not sure if this is a plugin bug or something else.
Is anything suspicious here?
Thanks!https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/-/issues/211Xorg crashes in AttendClient when compositor uses PresentPixmap2021-03-26T10:19:54ZyshuiXorg crashes in AttendClient when compositor uses PresentPixmapI have not narrowed down the root cause, but this is how I can reproduce this problem:
1. Clone https://github.com/yshui/compton, checkout the `split-backends` branch.
2. Build it
3. Run `compton --backend=xrender --vsync=opengl`.
4. Sc...I have not narrowed down the root cause, but this is how I can reproduce this problem:
1. Clone https://github.com/yshui/compton, checkout the `split-backends` branch.
2. Build it
3. Run `compton --backend=xrender --vsync=opengl`.
4. Screen freezes
5. Wait for a while, then Ctrl-C
6. X server crashes
I can only reproduce this with the intel driver.https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/-/issues/210Screenshot applications do not work correctly with xf86-video-intel2022-11-17T13:45:18ZGuido IodiceScreenshot applications do not work correctly with xf86-video-intelScreenshot applications do not work correctly when Xorg uses xf86-video-intel. Trying to take a screenshot will take you to a previous screen, such as the desktop or a window, even of already closed applications. This happens with severa...Screenshot applications do not work correctly when Xorg uses xf86-video-intel. Trying to take a screenshot will take you to a previous screen, such as the desktop or a window, even of already closed applications. This happens with several applications on KDE like Spectacle and Ksnip.
Everything works correctly with the modesetting driver.
OS: Manjaro Linux
DE: KDE Plasma 5.21.3
System: Intel i5 11th Gen, GPU Iris Xehttps://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/33wrong colors & cursor gamma vs. modesetting/Wayland on RDNA22021-03-07T12:53:04Zaufkrawallwrong colors & cursor gamma vs. modesetting/Wayland on RDNA2Since I've swapped my RX 5700 XT with an RX 6800, some colors are very noticeably off with xf86-video-amdgpu. It is very noticeable with the top blue bar on GitHub where the last commit and the total number of commits are listed (Example...Since I've swapped my RX 5700 XT with an RX 6800, some colors are very noticeably off with xf86-video-amdgpu. It is very noticeable with the top blue bar on GitHub where the last commit and the total number of commits are listed (Example site: https://github.com/torvalds/linux ) . With xf86-video-amdgpu, the top bar's blue color is rather turquoise instead of the regular colder blue tone. This can't be captured in screenshots. When opening such a screenshot with xf86-video-amdgpu, it's still turquoise, whereas with modesetting DDX (or Wayland) it's the regular blue tone. For testing reasons, I forcefully deleted colord so no color adjustments could take place, but the issue was unchanged. It happens also in every browser and also with color calibration turned off (e.g. gfx.color_management.mode = 0 in Firefox).
Perhaps another aspect of the same issue: There seems to be a too dark gamma applied to the hardware cursor. This is not visible with many typical desktop cursor themes which are either black or white, but e.g. when games change the cursor theme this gets apparent. This also only occurs with xf86-video-amdgpu and only since the RDNA2 card is installed.
Tested with Linux 5.11 and 5.12-rc1* (*should not be used with swap). I've also tested without any kernel command line argument like custom EDID. Arch Linux, Xorg 1.20.10, xf86-video-amdgpu 19.1 & git-master.
[Xorg.0.log](/uploads/675ec573e803d0a456d35789d6411617/Xorg.0.log)https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/32AMD rx560 could not boot into desktop.2021-03-04T20:50:05Znetroby1AMD rx560 could not boot into desktop.Hello, i fill this issue, because xorg amdgpu driver broken for AMD rx560 ,
I tried install many linux distro, both them failed to boot into desktop, (xorg seems not working, i think it was a amd gpu driver problem)
The affected distro...Hello, i fill this issue, because xorg amdgpu driver broken for AMD rx560 ,
I tried install many linux distro, both them failed to boot into desktop, (xorg seems not working, i think it was a amd gpu driver problem)
The affected distro:
Ubuntu 18.04, to Ubuntu 20.10
Linut mint 19.3, 20.1 (With mate , linuxmint cinnamon) LMDE 4,
Fedora linux 33
x86_64 arch.
The product link: https://item.m.jd.com/product/8413442.html?wxa_abtest=b&utm_user=plusmember&gx=RnE2wTEKbDWLmNRL-sA1AgOz&ad_od=share&utm_source=androidapp&utm_medium=appshare&utm_campaign=t_335139774&utm_term=CopyURL
华擎(ASRock)RX560 4G 幻影国度 钻石版 Phantom Gaming 1176-1223 MHz/7000 MHz 4GB GDDR5 显卡
I can only login into linux rescure mode.
and i also see the syslog,
looks the xsesssion was terminated due to some segmentfault.
The same hardware, which running windows 10 well.
so the hardware has no problem i guess.https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/31Crash when plug or unplug HDMI cable on a Zephyrus G14 with AMD integrated GPU2021-03-03T16:06:44ZPatrik DufreseCrash when plug or unplug HDMI cable on a Zephyrus G14 with AMD integrated GPUHard to tell what relevent information should be pass here.
I'm running a Zephyrus G14 Laptop with AMD GPU and NVidia GPU.
I'm running Linux pop-os 5.11.0-051100-generic #202102142330 SMP Sun Feb 14 23:33:21 UTC 2021 x86_64 x86_64 x86_...Hard to tell what relevent information should be pass here.
I'm running a Zephyrus G14 Laptop with AMD GPU and NVidia GPU.
I'm running Linux pop-os 5.11.0-051100-generic #202102142330 SMP Sun Feb 14 23:33:21 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
While running only with integrated GPU (AMDGPU only). Plug and plug the HDMI cable get the system freeze.
Here the dmesg dump:
```
[ 280.236488] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:70:crtc-1] flip_done timed out
[ 281.004456] [drm:do_aquire_global_lock.isra.0 [amdgpu]] *ERROR* [CRTC:70:crtc-1] hw_done or flip_done timed out
[ 291.244536] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:70:crtc-1] flip_done timed out
[ 301.484906] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:50:plane-2] flip_done timed out
[ 301.506995] [drm] Failed to add display topology, DTM TA is not initialized.
[ 301.536902] ------------[ cut here ]------------
[ 301.536910] WARNING: CPU: 11 PID: 191 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7754 amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0 [amdgpu]
[ 301.537315] Modules linked in: rfcomm xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink br_netfilter bridge stp llc ccm cmac algif_hash algif_skcipher af_alg snd_seq_dummy snd_hrtimer bnep btusb btrtl btbcm btintel bluetooth ecdh_generic ecc input_leds overlay intel_rapl_msr intel_rapl_common joydev snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence edac_mce_amd snd_hda_codec snd_hda_core snd_hwdep soundwire_bus snd_soc_core iwlmvm snd_compress ac97_bus snd_pcm_dmaengine mac80211 snd_pcm libarc4 snd_seq_midi snd_seq_midi_event snd_rawmidi kvm_amd snd_seq nls_iso8859_1 iwlwifi kvm snd_seq_device snd_timer asus_nb_wmi hid_multitouch wmi_bmof k10temp efi_pstore ccp rapl cfg80211 snd snd_rn_pci_acp3x soundcore
[ 301.537405] snd_pci_acp3x ucsi_acpi typec_ucsi typec asus_wireless mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear system76_io(OE) system76_acpi(OE) hid_asus asus_wmi sparse_keymap usbhid hid_generic amdgpu iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm aesni_intel crypto_simd cryptd glue_helper nvme ahci nvme_core libahci i2c_piix4 xhci_pci xhci_pci_renesas wmi video i2c_hid hid
[ 301.537482] CPU: 11 PID: 191 Comm: kworker/11:1 Tainted: G OE 5.11.0-051100-generic #202102142330
[ 301.537488] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IU_GA401IU/GA401IU, BIOS GA401IU.212 05/08/2020
[ 301.537493] Workqueue: events dm_irq_work_func [amdgpu]
[ 301.537844] RIP: 0010:amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0 [amdgpu]
[ 301.538183] Code: ff 48 8b 45 a8 48 c7 c7 12 d9 b0 c0 4c 89 55 80 8b b0 f0 03 00 00 e8 50 8a d1 ff 0f b6 55 a3 4c 8b 55 80 e9 24 fa ff ff 0f 0b <0f> 0b e9 89 fe ff ff 0f 0b e9 a2 fe ff ff e8 ae 42 ff e4 66 66 2e
[ 301.538187] RSP: 0018:ffffab49805f39f0 EFLAGS: 00010002
[ 301.538192] RAX: 0000000000000293 RBX: 0000000000000004 RCX: 00000000000005c6
[ 301.538194] RDX: 0000000000000001 RSI: 0000000000000293 RDI: ffff9f2b57120188
[ 301.538197] RBP: ffffab49805f3ab0 R08: 0000000000000002 R09: 0000000000000001
[ 301.538199] R10: 0000000000000000 R11: ffff9f2b58c60118 R12: 0000000000000293
[ 301.538201] R13: ffff9f2b58c60000 R14: ffff9f2bf567eb80 R15: ffff9f2b47451a00
[ 301.538204] FS: 0000000000000000(0000) GS:ffff9f2e5f8c0000(0000) knlGS:0000000000000000
[ 301.538207] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 301.538210] CR2: 00007f1006411000 CR3: 000000010de10000 CR4: 0000000000350ee0
[ 301.538213] Call Trace:
[ 301.538222] amdgpu_dm_atomic_commit_tail+0xc75/0x1260 [amdgpu]
[ 301.538557] ? __irq_work_queue_local+0x4f/0x60
[ 301.538566] ? irq_work_queue+0x2a/0x40
[ 301.538573] commit_tail+0x99/0x130 [drm_kms_helper]
[ 301.538602] drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper]
[ 301.538626] drm_atomic_commit+0x4a/0x50 [drm]
[ 301.538677] dm_force_atomic_commit.isra.0+0x93/0x120 [amdgpu]
[ 301.539018] dm_restore_drm_connector_state+0x54/0x60 [amdgpu]
[ 301.539367] handle_hpd_irq+0x11a/0x150 [amdgpu]
[ 301.539710] dm_irq_work_func+0x4e/0x60 [amdgpu]
[ 301.540039] process_one_work+0x220/0x3c0
[ 301.540048] worker_thread+0x50/0x370
[ 301.540051] kthread+0x12f/0x150
[ 301.540056] ? process_one_work+0x3c0/0x3c0
[ 301.540059] ? __kthread_bind_mask+0x70/0x70
[ 301.540064] ret_from_fork+0x22/0x30
[ 301.540074] ---[ end trace 2cd88f15afd49fee ]---
[ 301.540145] ------------[ cut here ]------------
[ 301.540146] WARNING: CPU: 11 PID: 191 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7354 amdgpu_dm_commit_planes.constprop.0+0x9d6/0x9f0 [amdgpu]
[ 301.540479] Modules linked in: rfcomm xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink br_netfilter bridge stp llc ccm cmac algif_hash algif_skcipher af_alg snd_seq_dummy snd_hrtimer bnep btusb btrtl btbcm btintel bluetooth ecdh_generic ecc input_leds overlay intel_rapl_msr intel_rapl_common joydev snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence edac_mce_amd snd_hda_codec snd_hda_core snd_hwdep soundwire_bus snd_soc_core iwlmvm snd_compress ac97_bus snd_pcm_dmaengine mac80211 snd_pcm libarc4 snd_seq_midi snd_seq_midi_event snd_rawmidi kvm_amd snd_seq nls_iso8859_1 iwlwifi kvm snd_seq_device snd_timer asus_nb_wmi hid_multitouch wmi_bmof k10temp efi_pstore ccp rapl cfg80211 snd snd_rn_pci_acp3x soundcore
[ 301.540662] snd_pci_acp3x ucsi_acpi typec_ucsi typec asus_wireless mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear system76_io(OE) system76_acpi(OE) hid_asus asus_wmi sparse_keymap usbhid hid_generic amdgpu iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm aesni_intel crypto_simd cryptd glue_helper nvme ahci nvme_core libahci i2c_piix4 xhci_pci xhci_pci_renesas wmi video i2c_hid hid
[ 301.540738] CPU: 11 PID: 191 Comm: kworker/11:1 Tainted: G W OE 5.11.0-051100-generic #202102142330
[ 301.540744] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IU_GA401IU/GA401IU, BIOS GA401IU.212 05/08/2020
[ 301.540749] Workqueue: events dm_irq_work_func [amdgpu]
[ 301.541084] RIP: 0010:amdgpu_dm_commit_planes.constprop.0+0x9d6/0x9f0 [amdgpu]
[ 301.541426] Code: c7 12 d9 b0 c0 4c 89 55 80 8b b0 f0 03 00 00 e8 50 8a d1 ff 0f b6 55 a3 4c 8b 55 80 e9 24 fa ff ff 0f 0b 0f 0b e9 89 fe ff ff <0f> 0b e9 a2 fe ff ff e8 ae 42 ff e4 66 66 2e 0f 1f 84 00 00 00 00
[ 301.541430] RSP: 0018:ffffab49805f39f0 EFLAGS: 00010086
[ 301.541435] RAX: 0000000000000001 RBX: 0000000000000004 RCX: 00000000000005c6
[ 301.541437] RDX: 0000000000000001 RSI: 0000000000000293 RDI: ffff9f2b57120188
[ 301.541439] RBP: ffffab49805f3ab0 R08: 0000000000000002 R09: 0000000000000001
[ 301.541441] R10: 0000000000000000 R11: ffff9f2b58c60118 R12: 0000000000000293
[ 301.541443] R13: ffff9f2b58c60000 R14: ffff9f2bf567eb80 R15: ffff9f2b47451a00
[ 301.541446] FS: 0000000000000000(0000) GS:ffff9f2e5f8c0000(0000) knlGS:0000000000000000
[ 301.541449] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 301.541452] CR2: 00007f1006411000 CR3: 000000010de10000 CR4: 0000000000350ee0
[ 301.541455] Call Trace:
[ 301.541460] amdgpu_dm_atomic_commit_tail+0xc75/0x1260 [amdgpu]
[ 301.541792] ? __irq_work_queue_local+0x4f/0x60
[ 301.541800] ? irq_work_queue+0x2a/0x40
[ 301.541808] commit_tail+0x99/0x130 [drm_kms_helper]
[ 301.541836] drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper]
[ 301.541860] drm_atomic_commit+0x4a/0x50 [drm]
[ 301.541911] dm_force_atomic_commit.isra.0+0x93/0x120 [amdgpu]
[ 301.542249] dm_restore_drm_connector_state+0x54/0x60 [amdgpu]
[ 301.542580] handle_hpd_irq+0x11a/0x150 [amdgpu]
[ 301.542908] dm_irq_work_func+0x4e/0x60 [amdgpu]
[ 301.543234] process_one_work+0x220/0x3c0
[ 301.543240] worker_thread+0x50/0x370
[ 301.543244] kthread+0x12f/0x150
[ 301.543249] ? process_one_work+0x3c0/0x3c0
[ 301.543252] ? __kthread_bind_mask+0x70/0x70
[ 301.543256] ret_from_fork+0x22/0x30
[ 301.543265] ---[ end trace 2cd88f15afd49fef ]---
```https://gitlab.freedesktop.org/xorg/driver/xf86-video-mga/-/issues/20mga2085 missing in the list of support cards. Intentional or by mistake?2021-03-02T20:14:57ZStefan B.mga2085 missing in the list of support cards. Intentional or by mistake?In mga.h in the list of PCI ID #defines, there is one card/chip
#define PCI_CHIP_MGA2085 0x0518
which is missing in the mga_driver.c file, in the MGAChipsets array.
May I ask whether this is intentional, maybe due to inc...In mga.h in the list of PCI ID #defines, there is one card/chip
#define PCI_CHIP_MGA2085 0x0518
which is missing in the mga_driver.c file, in the MGAChipsets array.
May I ask whether this is intentional, maybe due to incompatibilities of that card, or perhaps in error?https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/-/issues/209xorg assert failure pScreen->myNum - GPU_SCREEN_OFFSET < xf86NumGPUScreens fa...2022-01-05T23:36:23ZCyrille Giquelloxorg assert failure pScreen->myNum - GPU_SCREEN_OFFSET < xf86NumGPUScreens failedHello
I often encored the error `xorg assert failure: Xorg: .../hw/xfree86/common/xf86Helper.c:1740 xf86ScreenToScrn: Assertion pScreen->myNum - GPU_SCREEN_OFFSET < xf86NumGPUScreens failed`.
My config is:
- **2 displays**: laptop and ...Hello
I often encored the error `xorg assert failure: Xorg: .../hw/xfree86/common/xf86Helper.c:1740 xf86ScreenToScrn: Assertion pScreen->myNum - GPU_SCREEN_OFFSET < xf86NumGPUScreens failed`.
My config is:
- **2 displays**: laptop and an external lcd screen
- graphic card: **Mesa Intel Xe Graphics** (TGL GT2), UHD Graphics [8086:9a49] (rev 01)
- cpu: 11th Gen **Intel Core i7-1165G7**
- Linux ubuntu-NS50MU 5.8.0-44-generic #50-Ubuntu SMP Tue Feb 9 06:29:41 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
- Ubuntu 20.10, amd64, ubuntu:GNOME 3.38.3
- xserver-xorg-core 2:1.20.9-2ubuntu1.1
- client glx vendor string: Mesa Project and SGI, version string: 1.4
output of `Xorg -version`
```
X.Org X Server 1.20.9
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.15.0-124-generic x86_64 Ubuntu
Current Operating System: Linux ubuntu-NS50MU 5.8.0-44-generic #50-Ubuntu SMP Tue Feb 9 06:29:41 UTC 2021 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=735f8021-18dc-4f99-a529-ee6429facc2c ro quiet splash vt.handoff=7
Build Date: 30 November 2020 05:53:48PM
xorg-server 2:1.20.9-2ubuntu1.1 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.38.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
```
Some extract from glxinfo
```
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) Xe Graphics (TGL GT2) (0x9a49)
Version: 20.2.6
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.2.6
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.2.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
```
Thanks & cheers
Cyrille.https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/551System freeze: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]2021-12-17T14:21:02ZDimitri Papadopoulos OrfanosSystem freeze: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]I have been experiencing freezes on my Dell Precision Tower 3620 with NVidia GM107 graphics card and a large 3840 × 2160 screen for some years now, with both Ubuntu 18.04 and Ubuntu 20.04, possibly with Ubuntu 16.04 too - I cannot recall...I have been experiencing freezes on my Dell Precision Tower 3620 with NVidia GM107 graphics card and a large 3840 × 2160 screen for some years now, with both Ubuntu 18.04 and Ubuntu 20.04, possibly with Ubuntu 16.04 too - I cannot recall. It often happens while viewing video in vlc, but also during simpler tasks such as reading mails in Thunderbird.
Here are the contents of the `/var/log/syslog` at the time of the freeze;
```
Feb 26 11:18:15 xxxxxxxx kernel: [15385.625416] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Feb 26 11:18:15 xxxxxxxx kernel: [15385.625436] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
Feb 26 11:18:15 xxxxxxxx kernel: [15385.625453] nouveau 0000:01:00.0: fifo: channel 6: killed
Feb 26 11:18:15 xxxxxxxx kernel: [15385.625462] nouveau 0000:01:00.0: fifo: engine 5: scheduled for recovery
Feb 26 11:18:15 xxxxxxxx kernel: [15385.625467] nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery
Feb 26 11:18:15 xxxxxxxx kernel: [15385.626095] nouveau 0000:01:00.0: Xorg[2366]: channel 6 killed!
```
Mouse cursor stops moving, keyboard stops responding, virtual terminals cannot switch. Music continues to play. Sometimes I'm still able to log into the machine using ssh, sometimes I cannot even log in.
By the way, I don't know if it's related, but I'm mentioning this here for the sake of completeness: sometimes the screen starts flickering, the only way to fix that is to kill `Xorg`.https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/-/issues/208Bug triggered ?: intel and/or glamor2023-07-25T18:06:23ZRémi ESSAISSIBug triggered ?: intel and/or glamorHello,
Since the introduction of Asynchronous page-flipping, in Linux kernel 5.11,
Adding some code like:
...
mode_config->funcs = &intel_mode_funcs;
if (INTEL_GEN(i915) >= 9)
mode_config->async_page_fl...Hello,
Since the introduction of Asynchronous page-flipping, in Linux kernel 5.11,
Adding some code like:
...
mode_config->funcs = &intel_mode_funcs;
if (INTEL_GEN(i915) >= 9)
mode_config->async_page_flip = true;
...
in linux-5.11/drivers/gpu/drm/i915/display/intel_display.c
Makes Xorg hang : video and keyboard/mouse .
The faulty module is Glamor, which by disabeling it, makes Xorg dont hang while using openGL applications.
The error messages are tens of thousands of this:
modeset(0): flip queue failed: Invalid argument
modeset(0): Page flip failed: Invalid argument
modeset(0): present flip failed
Regards
X.Org X Server 1.20.10
Module glamoregl 1.0.1https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/33Trackpoint scrolling on the Thinkpad Trackpoint Keyboard 2 issues a middle mo...2021-03-04T06:50:38ZEmilioAKTrackpoint scrolling on the Thinkpad Trackpoint Keyboard 2 issues a middle mouse clickPressing middle mouse and holding it down acts as expected. But as soon as I move the Trackpoint it issues a middle mouse click, and then scrolls. I've verified this using xorg-xev on Arch.Pressing middle mouse and holding it down acts as expected. But as soon as I move the Trackpoint it issues a middle mouse click, and then scrolls. I've verified this using xorg-xev on Arch.https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/-/issues/207Commit 31486f40f causes rendering problems2021-01-24T16:06:42ZTaegil BaeCommit 31486f40f causes rendering problemsWith commit 31486f40f, some areas are flickering, and images and texts are distorted.
My system is Thinkpad X230 (HD 4000), external monitor, Arch Linux, Gnome 3.38.3 (Xorg and Wayland both are affected).
Is xf86-video-intel used in wa...With commit 31486f40f, some areas are flickering, and images and texts are distorted.
My system is Thinkpad X230 (HD 4000), external monitor, Arch Linux, Gnome 3.38.3 (Xorg and Wayland both are affected).
Is xf86-video-intel used in wayland? If I build xf86-video-intel with that commit, this issue occurs.https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/-/issues/206Revert to SW cursor when XRandR transformation enlarges beyond HW cursor2021-01-15T18:16:02ZiamahumanRevert to SW cursor when XRandR transformation enlarges beyond HW cursorXRandR scaling may change the cursor size as well, which the driver did not correctly handle.
When cursor.size (current cursor) grows beyond cursor.max_size (HW cursor size), `__sna_get_cursor` proceeds to copy the cursor into the preal...XRandR scaling may change the cursor size as well, which the driver did not correctly handle.
When cursor.size (current cursor) grows beyond cursor.max_size (HW cursor size), `__sna_get_cursor` proceeds to copy the cursor into the preallocated cursor buffer anyway, resulting in a buffer overrun.
Fix this by using the opportunity in `sna_cursors_reload` (CRTC config reload) to detect changes in transformed cursor size;
```patch
diff --git a/src/sna/sna_display.c b/src/sna/sna_display.c
index 874292bc..fb46ea1b 100644
--- a/src/sna/sna_display.c
+++ b/src/sna/sna_display.c
@@ -6223,6 +6223,12 @@ static struct sna_cursor *__sna_get_cursor(struct sna *sna, xf86CrtcPtr crtc)
} else
size = sna->cursor.size;
+ if (size > sna->cursor.max_size) {
+ __DBG(("%s: refusing to create cursor of size=%d, max=%d\n",
+ __FUNCTION__, size, sna->cursor.max_size));
+ return NULL;
+ }
+
if (crtc->transform_in_use) {
RRTransformPtr T = NULL;
struct pixman_vector v;
@@ -6828,6 +6834,26 @@ transformable_cursor(struct sna *sna, CursorPtr cursor)
return true;
}
+static bool __sna_cursor_possible(struct sna *sna, CursorPtr cursor)
+{
+ assert(cursor);
+ assert(sna->cursor.size == __cursor_size(cursor->bits->width, cursor->bits->height));
+
+ if (sna->cursor.size > sna->cursor.max_size) {
+ DBG(("%s: cursor size=%d too large, max %d: using sw cursor\n",
+ __FUNCTION__, sna->cursor.size, sna->cursor.max_size));
+ return false;
+ }
+
+ if (sna->mode.rr_active && !transformable_cursor(sna, cursor)) {
+ DBG(("%s: RandR active [%d] and non-transformable cursor: using sw cursor\n",
+ __FUNCTION__, sna->mode.rr_active));
+ return false;
+ }
+
+ return true;
+}
+
static Bool
sna_use_hw_cursor(ScreenPtr screen, CursorPtr cursor)
{
@@ -6850,15 +6876,8 @@ sna_use_hw_cursor(ScreenPtr screen, CursorPtr cursor)
sna->cursor.size =
__cursor_size(cursor->bits->width, cursor->bits->height);
- if (sna->cursor.size > sna->cursor.max_size) {
- DBG(("%s: cursor size=%d too large, max %d: using sw cursor\n",
- __FUNCTION__, sna->cursor.size, sna->cursor.max_size));
- return FALSE;
- }
-
- if (sna->mode.rr_active && !transformable_cursor(sna, cursor)) {
- DBG(("%s: RandR active [%d] and non-transformable cursor: using sw cursor\n",
- __FUNCTION__, sna->mode.rr_active));
+ if (!__sna_cursor_possible(sna, cursor)) {
+ DBG(("%s: cursor too large, using sw cursor\n", __FUNCTION__));
return FALSE;
}
@@ -7003,10 +7022,19 @@ static void
sna_cursors_reload(struct sna *sna)
{
DBG(("%s: active?=%d\n", __FUNCTION__, sna->cursor.active));
- if (sna->cursor.active)
+ if (sna->cursor.active) {
+ if (sna->cursor.ref &&
+ !__sna_cursor_possible(sna, sna->cursor.ref)) {
+ DBG(("%s: CRTC change incompatible with hw cursors, disabling\n", __FUNCTION__));
+ sna->cursor.disable = true;
+ restore_swcursor(sna);
+ return;
+ }
+
sna_set_cursor_position(sna->scrn,
sna->cursor.last_x,
sna->cursor.last_y);
+ }
}
static void
```https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/30Most colours are pink2021-01-08T11:20:40ZJPIE108Most colours are pinkI have a MSI RX 5700XT MECH OC and when I boot into any distro, the screen immediately turns pink after initramfs. The screen is still interactive and I still can use my system but most colours are pink. I have tested this on several dis...I have a MSI RX 5700XT MECH OC and when I boot into any distro, the screen immediately turns pink after initramfs. The screen is still interactive and I still can use my system but most colours are pink. I have tested this on several distros and they all seem to have this issue. My graphics card does work in my windows install and uefi bios.![issue](/uploads/b5e0a744c375f0a9e478db6e6e55b1a6/issue.jpg)https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/29error: ‘DPMSModeOn’ undeclared2020-12-18T15:08:11Zshoober420error: ‘DPMSModeOn’ undeclaredWhen trying to build against xorg-server-devel git master (https://gitlab.freedesktop.org/xorg/xserver/-/commit/65673b02ef28884da3267fe1be579c20e2cddfa6), an error will occur.
```
CC amdgpu_kms.lo
In file included from amdgpu_drv....When trying to build against xorg-server-devel git master (https://gitlab.freedesktop.org/xorg/xserver/-/commit/65673b02ef28884da3267fe1be579c20e2cddfa6), an error will occur.
```
CC amdgpu_kms.lo
In file included from amdgpu_drv.h:78,
from amdgpu_dri3.c:29:
drmmode_display.h: In function ‘drmmode_crtc_can_flip’:
drmmode_display.h:198:30: error: ‘DPMSModeOn’ undeclared (first use in this function); did you mean ‘DMTModes’?
198 | drmmode_crtc->dpms_mode == DPMSModeOn &&
| ^~~~~~~~~~
| DMTModes
```
I attached the log file.
[xf86-video-amdgpu-nosystemd-git-19.1.0.23-1-x86_64-build.log](/uploads/51860dc3fa0c83fd6948bc64920b9287/xf86-video-amdgpu-nosystemd-git-19.1.0.23-1-x86_64-build.log)https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/issues/11uxa_get_image in uxa-accel.c x/y wrong use. [Box.x1 = pDrawable->y + x + xo...2020-12-15T03:31:42Zxuyinguxa_get_image in uxa-accel.c x/y wrong use. [Box.x1 = pDrawable->y + x + xoff]- > [Box.x1 = pDrawable->x + x + xoff]`void
uxa_get_image(DrawablePtr pDrawable, int x, int y, int w, int h,
unsigned int format, unsigned long planeMask, char *d)
{
ScreenPtr screen = pDrawable->pScreen;
uxa_screen_t *uxa_screen = uxa_get_screen(screen);
BoxRec Bo...`void
uxa_get_image(DrawablePtr pDrawable, int x, int y, int w, int h,
unsigned int format, unsigned long planeMask, char *d)
{
ScreenPtr screen = pDrawable->pScreen;
uxa_screen_t *uxa_screen = uxa_get_screen(screen);
BoxRec Box;
PixmapPtr pPix = uxa_get_drawable_pixmap(pDrawable);
int xoff, yoff;
Bool ok;
RegionRec region;
uxa_get_drawable_deltas(pDrawable, pPix, &xoff, &yoff);
Box.x1 = pDrawable->y + x + xoff; // the pDrawable->y is wrong here, use pDrawable->x instead
Box.y1 = pDrawable->y + y + yoff;`