driver issueshttps://gitlab.freedesktop.org/groups/xorg/driver/-/issues2020-09-15T09:23:09Zhttps://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/21Dual-monitor setup broken since commit cfce4b3e: Drop bo/width/height members...2020-09-15T09:23:09ZJohannes HirteDual-monitor setup broken since commit cfce4b3e: Drop bo/width/height members from struct drmmode_scanoutSince commit cfce4b3e6b05b1be14b7ce716dbfb9a15e7e21f4
Author: Michel Dänzer <mdaenzer@redhat.com>
Date: Tue Apr 21 18:48:06 2020 +0200
Drop bo/width/height members from struct drmmode_scanout
The pixmap is all we really n...Since commit cfce4b3e6b05b1be14b7ce716dbfb9a15e7e21f4
Author: Michel Dänzer <mdaenzer@redhat.com>
Date: Tue Apr 21 18:48:06 2020 +0200
Drop bo/width/height members from struct drmmode_scanout
The pixmap is all we really need.
dual-monitor setup is broken for some configurations. I've an laptop with 1920x1080 native resolution connected via eDP. When adding a second monitor, the screen gets garbled there. The Monitor has a native resolution of 1680x1050 and is connected via HDMI-DVI (monitor is only DVI, laptop has only HDMI). Going back to
commit 680b9a2976f9eb8010c8160c425c2194fb5429d1
Author: Niclas Zeising <zeising@daemonic.se>
Date: Wed Apr 15 10:34:32 2020 +0200
Fix return value check of drmIoctl()
When the drmModeSetCursor2() call was replaced with bare drmIoctl() call in
b344e155, a bug was introduced. With the use of drmModeSetCursor2(),
the return value from drmIoctl() (which calls ioctl()) were mangled, if
they were negative, they were replaced by -errno by a wrapper function
in xf86drMode.c in libdrm. After replacing drmModeSetCursor2() with the
call to drmIoctl(), this mangling no longer happens, and we need to
explicitly check if the call to drmIoctl() fails, which is indicated by
returning -1, and then why it failed, by checking errno.
If the error indicated by errno is EINVAL, then we can't use the
DRM_IOCTL_MODE_CURSOR2 ioctl(), and need to fall back to the
DRM_IOCTL_MODE_CURSOR ioctl().
This bug can manifest itself by an invisible hw cursor on systems where the
DRM_IOCTL_MODE_CURSOR2 is not implemented by the graphics driver.
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
solved this. Attaching a photo from the corrupted screen.
![DSC_0039](/uploads/6fa67edf9819c713e5e416b32fc4e69d/DSC_0039.JPG)20.0Michel DänzerMichel Dänzerhttps://gitlab.freedesktop.org/xorg/driver/xf86-video-mga/-/issues/19[Matrox G400 102b:0525] (EE) open /dev/dri/card0: No such file or directory (...2020-08-25T20:41:30ZFelix Miatamrmazda@earthlink.net[Matrox G400 102b:0525] (EE) open /dev/dri/card0: No such file or directory (Xorg fails to run with cmdline option vga= on vttys; except vga=normal works)downstream bug created 2019-07-31:
https://bugs.mageia.org/show_bug.cgi?id=25205
(EE) highlights from typical Xorg.0.log:
[ 116.801] (EE) open /dev/dri/card0: No such file or directory
[ 116.845] (EE) MGA(0): Unable to map Framebuff...downstream bug created 2019-07-31:
https://bugs.mageia.org/show_bug.cgi?id=25205
(EE) highlights from typical Xorg.0.log:
[ 116.801] (EE) open /dev/dri/card0: No such file or directory
[ 116.845] (EE) MGA(0): Unable to map Framebuffer F8000000 2000000. Invalid argument (22)
[ 116.887] (EE) MGA(0): Unable to detect video RAM.
[ 116.887] (EE) Screen(s) found, but none have a usable configuration.
[ 116.887] (EE)
[ 116.888] (EE) no screens found(EE)
To reproduce:
1-include any valid VGA= mode other than normal on kernel cmdline
Actual result:
1-X won't start
Expected result:
1-X runs normally
Comments:
1-without vga= something on cmdline, vttys are all confined to painfully limiting 80x25 mode
2-only 32-bit arches tested
3-Same apparent problem in Debian 10 & 11 as in Mageia 7 & 8
4-Cannot replicate problem in openSUSE Tumbleweed, as mga DDX won't load due to undefined symbol
Mageia 8: [Xorg.0.log](/uploads/550ff6ad3db11ade2870263b501f4afc/Xorg.0.log) (fail)
Tumbleweed: [Xorg.0.logT](/uploads/3d79681c6a5b0f9e4a40b31b536710f7/Xorg.0.logT)https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/20Screen flickering with ASUS TUF GAMING A15 laptop (FX506IV)2020-08-24T09:26:19ZJoonas CoataneaScreen flickering with ASUS TUF GAMING A15 laptop (FX506IV)Hi,
I'm currently experiencing a problem with the amdgpu driver that causes the screen to flicker (turn off and back on quickly) at a regular interval.
This also occurs with the modesetting driver.
Turning the screen off and back on agai...Hi,
I'm currently experiencing a problem with the amdgpu driver that causes the screen to flicker (turn off and back on quickly) at a regular interval.
This also occurs with the modesetting driver.
Turning the screen off and back on again using `xset dpms force off` fixes the issue, but the screen can start flickering again if it turns off and back on again afterwards (using `xset dpms force off` or due to inactivity).
Also, I get the following error in dmesg, whenever i use `xset dpms force off` to turn the screen off and back on again, or the screen turns off and back on again due to inactivity:
```
[ 2257.034515] [drm:dpcd_set_source_specific_data [amdgpu]] *ERROR* Error in DP aux read transaction, not writing source specific data
[ 2257.141722] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized.
[ 2257.141726] [drm] [Link 0] WARNING MOD_HDCP_STATUS_FAILURE IN STATE HDCP_UNINITIALIZED STAY COUNT 0
```
Here is my `Xorg.0.log` log file:
[https://pastebin.com/jDtEqj74](https://pastebin.com/jDtEqj74)
Here is my `dmesg` log:
[https://pastebin.com/E074CSsv](https://pastebin.com/E074CSsv)
In addition, here is a recording of the flickering:
[https://drive.google.com/file/d/1IIpwEVYmNsdKPkiB2042OZ7cvvJYqjob/view?usp=sharing](https://drive.google.com/file/d/1IIpwEVYmNsdKPkiB2042OZ7cvvJYqjob/view?usp=sharing)
System info:
Linux distribution: Arch Linux
Laptop name: ASUS TUF GAMING A15
Laptop model: FX506IV
CPU: AMD Ryzen 9 4900H with builtin Radeon graphics.
Discrete GPU: Nvidia Geforce RTX 2060
Screen: 144Hz screen with "adaptive sync" support (whether this is AMD's FreeSync or NVIDIA's GSYNC i am unsure)https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/546nouveau crash on shutdown 5.4.0-42-generic Ubuntu 20.04 vmmgf100.c:2212020-08-19T09:18:15ZJonnynouveau crash on shutdown 5.4.0-42-generic Ubuntu 20.04 vmmgf100.c:221The syslog has lots of other issues at the same time, but not the one in the photo of the terminal I will attach. A![crash_IMG_20200818_225159](/uploads/444ff90f232d823f497ab93427a1dbe6/crash_IMG_20200818_225159.jpg)ll very similar.
`A...The syslog has lots of other issues at the same time, but not the one in the photo of the terminal I will attach. A![crash_IMG_20200818_225159](/uploads/444ff90f232d823f497ab93427a1dbe6/crash_IMG_20200818_225159.jpg)ll very similar.
`Aug 18 22:24:28 asus kernel: [ 1235.807316] nouveau 0000:01:00.0: tmr: stalled at bad0da1fbad0da1f
Aug 18 22:24:28 asus kernel: [ 1235.807353] ------------[ cut here ]------------
Aug 18 22:24:28 asus kernel: [ 1235.807354] nouveau 0000:01:00.0: timeout
Aug 18 22:24:28 asus kernel: [ 1235.807425] WARNING: CPU: 7 PID: 2496 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:221 gf100_vmm_invalidate+0x1c2/0x1d0 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807427] Modules linked in: rfcomm vmnet(OE) vmw_vsock_vmci_transport vsock vboxnetadp(OE) vboxnetflt(OE) vmw_vmci vboxdrv(OE) vmmon(OE) cmac algif_hash algif_skcipher af_alg bnep binfmt_misc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp mei_hdcp snd_hda_codec_hdmi kvm_intel snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep uvcvideo crct10dif_pclmul snd_pcm videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common snd_seq_midi btrtl btbcm snd_seq_midi_event videodev btintel ghash_clmulni_intel bluetooth snd_rawmidi iwldvm mc snd_seq ecdh_generic mac80211 ecc aesni_intel nouveau crypto_simd libarc4 cryptd uas glue_helper usb_storage intel_cstate usblp snd_seq_device intel_rapl_perf i915 iwlwifi ttm snd_timer drm_kms_helper joydev asus_nb_wmi input_leds i2c_algo_bit asus_wmi snd fb_sys_fops syscopyarea sparse_keymap sysfillrect mei_me serio_raw mxm_wmi wmi_bmof
Aug 18 22:24:28 asus kernel: [ 1235.807452] sysimgblt cfg80211 soundcore mei mac_hid asus_wireless sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic usbhid hid crc32_pclmul alx mdio psmouse ahci lpc_ich libahci wmi video
Aug 18 22:24:28 asus kernel: [ 1235.807461] CPU: 7 PID: 2496 Comm: gst-plugin-scan Tainted: G W OE 5.4.0-42-generic #46-Ubuntu
Aug 18 22:24:28 asus kernel: [ 1235.807462] Hardware name: ASUSTeK COMPUTER INC. N56VB/N56VB, BIOS N56VB.202 01/21/2013
Aug 18 22:24:28 asus kernel: [ 1235.807495] RIP: 0010:gf100_vmm_invalidate+0x1c2/0x1d0 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807496] Code: 8b 40 10 48 8b 78 10 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 a0 c0 44 d3 4c 89 e2 48 c7 c7 2c 52 bc c0 48 89 c6 e8 29 32 df d2 <0f> 0b e9 58 ff ff ff e8 f2 2e df d2 66 90 0f 1f 44 00 00 8b 87 cc
Aug 18 22:24:28 asus kernel: [ 1235.807497] RSP: 0018:ffffb271818e3268 EFLAGS: 00010286
Aug 18 22:24:28 asus kernel: [ 1235.807498] RAX: 0000000000000000 RBX: ffff9cae97377800 RCX: 0000000000000006
Aug 18 22:24:28 asus kernel: [ 1235.807499] RDX: 0000000000000007 RSI: 0000000000000086 RDI: ffff9cae9edd78c0
Aug 18 22:24:28 asus kernel: [ 1235.807499] RBP: ffffb271818e32c8 R08: 0000000000000662 R09: 0000000000000004
Aug 18 22:24:28 asus kernel: [ 1235.807500] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9cae9c69d620
Aug 18 22:24:28 asus kernel: [ 1235.807500] R13: ffff9cae90985200 R14: ffff9cae90982620 R15: ffff9cae98d7f640
Aug 18 22:24:28 asus kernel: [ 1235.807501] FS: 00007f6bdc558340(0000) GS:ffff9cae9edc0000(0000) knlGS:0000000000000000
Aug 18 22:24:28 asus kernel: [ 1235.807502] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 18 22:24:28 asus kernel: [ 1235.807503] CR2: 000055da5b73e560 CR3: 0000000417b5e002 CR4: 00000000001606e0
Aug 18 22:24:28 asus kernel: [ 1235.807503] Call Trace:
Aug 18 22:24:28 asus kernel: [ 1235.807532] ? nv50_instobj_release+0x8b/0xa0 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807559] gf100_vmm_flush+0x1f/0x30 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807588] nvkm_vmm_iter.constprop.0+0x325/0x7e0 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807626] ? gf100_vmm_pgt_dma+0x300/0x300 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807652] ? nvkm_vmm_sparse_unref_ptes+0x80/0x80 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807678] nvkm_vmm_ptes_get_map+0x33/0x80 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807702] ? nvkm_vmm_sparse_unref_ptes+0x80/0x80 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807730] ? gf100_vmm_pgt_dma+0x300/0x300 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807755] nvkm_vmm_map+0x1e8/0x380 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807779] ? nvkm_vma_tail+0x50/0x150 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807801] nvkm_vram_map+0x58/0x80 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807825] nv50_instobj_map+0x19/0x20 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807848] nv50_instobj_kmap+0x16a/0x260 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807871] nv50_instobj_acquire+0x134/0x140 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807904] nvkm_instobj_new+0xd1/0x190 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807923] nvkm_memory_new+0x42/0x70 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807948] nvkm_mmu_ptc_get.part.0+0xbc/0x270 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.807982] nvkm_mmu_ptc_get+0x2f/0x80 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808005] nvkm_vmm_ctor+0x286/0x390 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808028] nvkm_vmm_new_+0x69/0x90 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808052] nv04_vmm_new_+0x1a/0x40 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808076] gf100_vmm_new_+0x72/0x80 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808100] gk104_vmm_new+0x39/0x40 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808124] nvkm_uvmm_new+0x15c/0x1a0 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808141] nvkm_ioctl_new+0x167/0x210 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808168] ? nvkm_uvmm_search+0x30/0x30 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808186] nvkm_ioctl+0xf0/0x190 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808215] nvkm_client_ioctl+0x12/0x20 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808231] nvif_object_ioctl+0x4e/0x60 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808247] nvif_object_init+0xda/0x140 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808264] nvif_vmm_init+0xb0/0x230 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808293] nouveau_vmm_init+0x32/0x50 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808321] nouveau_cli_init+0x325/0x450 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808349] nouveau_drm_open+0xe1/0x180 [nouveau]
Aug 18 22:24:28 asus kernel: [ 1235.808361] drm_file_alloc+0x180/0x220 [drm]
Aug 18 22:24:28 asus kernel: [ 1235.808368] drm_open+0x9f/0x190 [drm]
Aug 18 22:24:28 asus kernel: [ 1235.808376] drm_stub_open+0xb6/0x110 [drm]
Aug 18 22:24:28 asus kernel: [ 1235.808379] chrdev_open+0xd3/0x1c0
Aug 18 22:24:28 asus kernel: [ 1235.808380] ? cdev_default_release+0x20/0x20
Aug 18 22:24:28 asus kernel: [ 1235.808382] do_dentry_open+0x143/0x3a0
Aug 18 22:24:28 asus kernel: [ 1235.808383] vfs_open+0x2d/0x30
Aug 18 22:24:28 asus kernel: [ 1235.808385] do_last+0x194/0x900
Aug 18 22:24:28 asus kernel: [ 1235.808386] path_openat+0x8d/0x290
Aug 18 22:24:28 asus kernel: [ 1235.808388] ? uevent_show+0xe2/0x100
Aug 18 22:24:28 asus kernel: [ 1235.808390] do_filp_open+0x91/0x100
Aug 18 22:24:28 asus kernel: [ 1235.808391] ? __alloc_fd+0x46/0x150
Aug 18 22:24:28 asus kernel: [ 1235.808392] do_sys_open+0x17e/0x290
Aug 18 22:24:28 asus kernel: [ 1235.808394] __x64_sys_openat+0x20/0x30
Aug 18 22:24:28 asus kernel: [ 1235.808396] do_syscall_64+0x57/0x190
Aug 18 22:24:28 asus kernel: [ 1235.808398] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug 18 22:24:28 asus kernel: [ 1235.808399] RIP: 0033:0x7f6bdc8c8d1b
Aug 18 22:24:28 asus kernel: [ 1235.808401] Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 48 8b 4c 24 28 64 48 33 0c 25
Aug 18 22:24:28 asus kernel: [ 1235.808401] RSP: 002b:00007ffdd9cd9570 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
Aug 18 22:24:28 asus kernel: [ 1235.808402] RAX: ffffffffffffffda RBX: 000055da5b73a060 RCX: 00007f6bdc8c8d1b
Aug 18 22:24:28 asus kernel: [ 1235.808403] RDX: 0000000000080002 RSI: 000055da5b73bbc0 RDI: 00000000ffffff9c
Aug 18 22:24:28 asus kernel: [ 1235.808403] RBP: 000055da5b73bbc0 R08: 00007f6bdc400bf0 R09: 000055da5b73be80
Aug 18 22:24:28 asus kernel: [ 1235.808404] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000080002
Aug 18 22:24:28 asus kernel: [ 1235.808404] R13: 00007f6bdc551e30 R14: 000055da5b716330 R15: 00007f6bdc5300b4
Aug 18 22:24:28 asus kernel: [ 1235.808406] ---[ end trace c7f1d8742a68dcf1 ]---
Aug 18 22:24:28 asus rtkit-daemon[1617]: Recovering from system lockup, not allowing further RT threads.
Aug 18 22:24:28 asus systemd[2432]: Starting D-Bus User Message Bus Socket.
Aug 18 22:24:28 asus kernel: [ 1235.848584] nouveau 0000:01:00.0: tmr: stalled at bad0da1fbad0da1f`https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/19Crash when playing a game in Wine2020-08-17T13:37:12ZKoz RossCrash when playing a game in WineWhen entering a particular area in a game (emulated in Wine), I consistently get a crash from AMDGPU, which brings down the X server session. `dmesg` gives the following output:
```
[10203.155500] [drm:amdgpu_dm_atomic_commit_tail [amdg...When entering a particular area in a game (emulated in Wine), I consistently get a crash from AMDGPU, which brings down the X server session. `dmesg` gives the following output:
```
[10203.155500] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
[10207.965475] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=4350833, emitted seq=4350835
[10207.965517] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process ed8.exe pid 22385 thread ed8.exe pid 22385
[10207.965520] amdgpu 0000:01:00.0: GPU reset begin!
[10208.195500] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
[10208.725895] cp is busy, skip halt cp
[10208.913906] rlc is busy, skip halt rlc
[10208.914924] amdgpu 0000:01:00.0: GPU BACO reset
[10209.087420] amdgpu 0000:01:00.0: GPU reset succeeded, trying to resume
[10209.087912] [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
[10209.087920] [drm] VRAM is lost due to GPU reset!
[10209.463971] [drm] UVD and UVD ENC initialized successfully.
[10209.565006] [drm] VCE initialized successfully.
[10209.571493] [drm] recover vram bo from shadow start
[10209.581769] [drm] recover vram bo from shadow done
[10209.581771] [drm] Skip scheduling IBs!
[10209.581772] [drm] Skip scheduling IBs!
[10209.581788] [drm] Skip scheduling IBs!
[10209.581792] [drm] Skip scheduling IBs!
[10209.581795] [drm] Skip scheduling IBs!
[10209.581797] [drm] Skip scheduling IBs!
[10209.581799] [drm] Skip scheduling IBs!
[10209.581801] [drm] Skip scheduling IBs!
[10209.581803] [drm] Skip scheduling IBs!
[10209.581806] amdgpu 0000:01:00.0: GPU reset(2) succeeded!
[10209.581806] [drm] Skip scheduling IBs!
[10209.581808] [drm] Skip scheduling IBs!
[10209.581809] [drm] Skip scheduling IBs!
[10209.581811] [drm] Skip scheduling IBs!
[10209.581813] [drm] Skip scheduling IBs!
[10209.581814] [drm] Skip scheduling IBs!
[10209.581816] [drm] Skip scheduling IBs!
[10209.581817] [drm] Skip scheduling IBs!
[10209.581818] [drm] Skip scheduling IBs!
[10209.581819] [drm] Skip scheduling IBs!
[10209.581820] [drm] Skip scheduling IBs!
[10209.581821] [drm] Skip scheduling IBs!
[10209.581823] [drm] Skip scheduling IBs!
[10209.581824] [drm] Skip scheduling IBs!
[10209.581825] [drm] Skip scheduling IBs!
[10209.581826] [drm] Skip scheduling IBs!
[10209.581827] [drm] Skip scheduling IBs!
[10209.581828] [drm] Skip scheduling IBs!
[10209.581829] [drm] Skip scheduling IBs!
[10209.581830] [drm] Skip scheduling IBs!
[10209.581831] [drm] Skip scheduling IBs!
[10209.581832] [drm] Skip scheduling IBs!
[10209.581833] [drm] Skip scheduling IBs!
[10209.581834] [drm] Skip scheduling IBs!
[10209.581835] [drm] Skip scheduling IBs!
[10209.581836] [drm] Skip scheduling IBs!
[10209.581837] [drm] Skip scheduling IBs!
[10209.581838] [drm] Skip scheduling IBs!
[10209.581839] [drm] Skip scheduling IBs!
[10209.581840] [drm] Skip scheduling IBs!
[10209.581841] [drm] Skip scheduling IBs!
[10209.581842] [drm] Skip scheduling IBs!
[10209.581843] [drm] Skip scheduling IBs!
[10209.581844] [drm] Skip scheduling IBs!
[10209.581844] [drm] Skip scheduling IBs!
[10209.581846] [drm] Skip scheduling IBs!
[10209.581847] [drm] Skip scheduling IBs!
[10209.581848] [drm] Skip scheduling IBs!
[10209.581849] [drm] Skip scheduling IBs!
[10209.581850] [drm] Skip scheduling IBs!
[10209.581852] [drm] Skip scheduling IBs!
[10209.581853] [drm] Skip scheduling IBs!
[10209.581854] [drm] Skip scheduling IBs!
[10209.581855] [drm] Skip scheduling IBs!
[10209.581856] [drm] Skip scheduling IBs!
[10209.581858] [drm] Skip scheduling IBs!
[10209.581859] [drm] Skip scheduling IBs!
[10209.581860] [drm] Skip scheduling IBs!
[10209.581861] [drm] Skip scheduling IBs!
[10209.581862] [drm] Skip scheduling IBs!
[10209.581864] [drm] Skip scheduling IBs!
[10209.581866] [drm] Skip scheduling IBs!
[10209.581866] [drm] Skip scheduling IBs!
[10209.581868] [drm] Skip scheduling IBs!
[10209.581869] [drm] Skip scheduling IBs!
[10209.581870] [drm] Skip scheduling IBs!
[10209.581871] [drm] Skip scheduling IBs!
[10209.581872] [drm] Skip scheduling IBs!
[10209.581873] [drm] Skip scheduling IBs!
[10209.582206] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[10214.873869] libobs: graphic[21353]: segfault at 7f72743e0000 ip 00007f7282f27974 sp 00007f7227ab71e8 error 6 in radeonsi_dri.so[7f728219b000+df5000]
[10214.873881] Code: 8b 02 49 c1 e8 20 44 8d 58 01 44 89 1a 44 89 04 87 8b 02 44 8d 40 01 44 89 02 89 0c 87 8b 02 48 c1 e9 20 44 8d 40 01 44 89 02 <89> 0c 87 8b 02 8d 48 01 89 0a 44 89 0c 87 40 84 f6 74 22 41 83 e2
```
I'm on an RX 570 graphics card. Linux kernel version is 5.7.15 with the CK patch set. Mesa version is 20.1.5, AMDGPU version is 19.1.0. I'm running Arch Linux.https://gitlab.freedesktop.org/xorg/driver/xf86-video-v4l/-/issues/2Any plans to make new release?2020-08-15T01:56:53ZTomasz KłoczkoAny plans to make new release?I think that it would be good to flush currently committed changes and make new release :)I think that it would be good to flush currently committed changes and make new release :)https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/545Stale texture data and flicker in small SDL2 program2022-01-23T00:50:22ZKevin CahalanStale texture data and flicker in small SDL2 programVideo of bug: https://youtu.be/O0__VNN9G_o
At 0:11 in the video you see old web browser data showing up in my program.
At 0:19 when I close a window in my program the texture for my piano key letters
flicker. By luck the texture for my...Video of bug: https://youtu.be/O0__VNN9G_o
At 0:11 in the video you see old web browser data showing up in my program.
At 0:19 when I close a window in my program the texture for my piano key letters
flicker. By luck the texture for my keys sometimes flickers to stuff previously
displayed on my desktop. This flickering is linked to my mouse movement/placement.
When I run my program with the proprietary 440 NVIDIA driver things work fine. It also works fine with the opensource Intel video driver on a different computer.
I am on Ubuntu budgie 20.04 using XFCE on X.org X11.
The SDL2 program source:
https://github.com/kevinacahalan/piano_waterfall
git hash 553bb6c8ca18b23494a6c92f4551baa1649f0374
[kernel_log.txt](/uploads/9b4057f74becbef5b17b6611ba36f62a/kernel_log.txt)https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/544Artifacts in XFWM window decorations2020-08-05T12:57:36ZAlexanderArtifacts in XFWM window decorationsHello,
I'm using XFCE and recently had to ditch the proprietary Nvidia driver and switch to **nouveau** (I've got a pretty old GeForce 9500 GT and legacy drivers are not supported under new kernels).
The only thing that bugs me now is t...Hello,
I'm using XFCE and recently had to ditch the proprietary Nvidia driver and switch to **nouveau** (I've got a pretty old GeForce 9500 GT and legacy drivers are not supported under new kernels).
The only thing that bugs me now is that I see artifacts in window title bars.
Distribution: Void Linux (rolling distro). Fresh XFCE. No compositing.
Here is how it looks: http://0x0.st/ixst.png and http://0x0.st/ixnt.png. And here is how it should look: http://0x0.st/ixsv.png
It can be seen from the very start of the system. Logging out and logging back in solves the issue for me.
Here are my logs:
[dmesg.log](https://pastebin.com/raw/qYhSbYNu)
[Xorg.0.log](https://pastebin.com/raw/KjuEHYRM)
[lxdm.log](https://pastebin.com/raw/e1MX64gF)
Switching to kernel **modesetting** driver completely fixes the problem.
Is there anything I should provide for you?
Thank you.https://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/-/issues/12Can't set MinSpeed, MaxSpeed and AccelFactor in xorg.conf.d2020-08-05T05:25:23ZSylvain SCan't set MinSpeed, MaxSpeed and AccelFactor in xorg.conf.dHello,
First and foremost thank you for this amazing driver.
I've noticed that Synaptics simply ignore `MinSpeed`, `MaxSpeed` and `AccelFactor` in *xorg.conf.d/* :
```
$ cat /etc/X11/xorg.conf.d/70-synaptics.conf
Section "InputClass"
...Hello,
First and foremost thank you for this amazing driver.
I've noticed that Synaptics simply ignore `MinSpeed`, `MaxSpeed` and `AccelFactor` in *xorg.conf.d/* :
```
$ cat /etc/X11/xorg.conf.d/70-synaptics.conf
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchDevicePath "/dev/input/event*"
MatchIsTouchpad "on"
Option "TapButton1" "0"
Option "TapButton2" "0"
Option "TapButton3" "2"
Option "MinSpeed" "1.239900"
Option "MaxSpeed" "1.867536"
Option "AccelFactor" "0.090667"
# enable 'natural' scrolling
Option "VertScrollDelta" "-80"
Option "HorizScrollDelta" "-80"
EndSection
```
`synclient -l` does not show any modification pertaining to either of the 3 parameters.
```
$ synclient -l
...
MinSpeed = 1
MaxSpeed = 1.5062
AccelFactor = 0.090667
...
TapButton1 = 0
TapButton2 = 0
TapButton3 = 2
...
```
So the only way to modify these is `synclient MinSpeed=1.239 MaxSpeed=1.867 AccelFactor=0.090` or using `xinput`.
I'm really surprised this hasn't been spotted sooner. I hope you'll take my report in consideration.
Thank you!https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/-/issues/202Brief black screen when the screen is rotated in portrait mode (2-in-1 laptop)2020-09-15T11:00:36ZTuxman2Brief black screen when the screen is rotated in portrait mode (2-in-1 laptop)Hi Xorg Team,
I've got a 2-in-1 laptop (tablet/PC) and I noticed when the screen is rotate in portrait mode, there is a brief black screen who appears. This problem does not appear in 180° mode. It is only with Xorg/X11 and not with Way...Hi Xorg Team,
I've got a 2-in-1 laptop (tablet/PC) and I noticed when the screen is rotate in portrait mode, there is a brief black screen who appears. This problem does not appear in 180° mode. It is only with Xorg/X11 and not with Wayland. I guess Xorg/X11 is using xrandr for the screen rotation, and in fact, the screen must be resized in an other resolution because the display is different in portrait mode.
What I only want to know is if there is a fix to avoid that brief black screen when we tilt the screen in portrait mode when we use Xorg/X11 ?
Thanks.
Regards.
Note: I'm on Manjaro KDE with the last updates software versions available (last xorg version included). Tested with Intel video card available on the 2-in-1 laptop only.
The bug is still present: https://gitlab.freedesktop.org/xorg/xserver/-/issues/216https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/18Shader crashes session2020-08-03T14:37:37ZGhost UserShader crashes sessionThe following shader on Shadertoy.com crashes session and needs to be killed before PC is usable again:
!!! IF YOU FOLLOW THIS LINK YOU SESSION MIGHT CRASH !!!
[https://www.shadertoy.com/view/ttf3Dj](https://www.shadertoy.com/view/ttf3D...The following shader on Shadertoy.com crashes session and needs to be killed before PC is usable again:
!!! IF YOU FOLLOW THIS LINK YOU SESSION MIGHT CRASH !!!
[https://www.shadertoy.com/view/ttf3Dj](https://www.shadertoy.com/view/ttf3Dj)
Mutter/Gnome, Kernel 5.7, Firefox 79.0https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/543[Telsa] [G92GLM] WARNING: CPU: 4 PID: 2360 at lib/refcount.c:28 refcount_warn...2020-07-30T13:59:51Zgeaaru[Telsa] [G92GLM] WARNING: CPU: 4 PID: 2360 at lib/refcount.c:28 refcount_warn_saturate+0xab/0xf0With last kernels (4.x and 5.x) my Quadro card is a bit unusable.
This happens on Dell Precision M6500 with kernel vanilla 5.6.18.
```
[30843.780742] ------------[ cut here ]------------
[30843.780743] refcount_t: underflow; use-after-...With last kernels (4.x and 5.x) my Quadro card is a bit unusable.
This happens on Dell Precision M6500 with kernel vanilla 5.6.18.
```
[30843.780742] ------------[ cut here ]------------
[30843.780743] refcount_t: underflow; use-after-free.
[30843.780763] WARNING: CPU: 4 PID: 2360 at lib/refcount.c:28 refcount_warn_saturate+0xab/0xf0
[30843.780763] Modules linked in: ebtable_filter ebtables tun xt_nat veth xt_conntrack nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter ip6table_nat ip6table_mangle ip6table_filter ip6_tables xt_CHECKSUM iptable_mangle xt_comment xt_tcpudp bridge xt_MASQUERADE iptable_nat iptable_filter ip_tables x_tables bpfilter nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv4 crypto_simd cryptd glue_helper xts 8021q garp mrp stp llc xfs rfcomm fuse cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel bluetooth ecdh_generic ecc ext4 mbcache jbd2 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc sch_fq_codel iwldvm snd_hda_codec_idt snd_hda_codec_generic mac80211 ledtrig_audio joydev iTCO_wdt gpio_ich iTCO_vendor_support snd_hda_intel snd_intel_dspcfg iwlwifi snd_hda_codec intel_powerclamp coretemp snd_hda_core dell_wmi kvm_intel snd_hwdep dell_smbios dell_smm_hwmon snd_pcm kvm irqbypass pcspkr
[30843.780815] psmouse tifm_7xx1 input_leds sparse_keymap dell_wmi_descriptor i7core_edac i2c_i801 tifm_core lpc_ich cfg80211 snd_timer tg3 snd tpm_tis tpm_tis_core tpm zfs(PO) zunicode(PO) zlua(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ipv6 crc_ccitt nf_defrag_ipv6 uas hid_generic pcmcia crc32c_intel serio_raw sdhci_pci cqhci sdhci firewire_ohci xhci_pci mmc_core firewire_core yenta_socket xhci_hcd ehci_pci ehci_hcd nouveau mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm agpgart
[30843.780852] CPU: 4 PID: 2360 Comm: Xorg Tainted: P O 5.6.0-sabayon #1
[30843.780853] Hardware name: Dell Inc. Precision M6500 /0R1203, BIOS A10 06/04/2013
[30843.780857] RIP: 0010:refcount_warn_saturate+0xab/0xf0
[30843.780860] Code: 05 56 12 28 01 01 e8 46 ca c0 ff 0f 0b c3 80 3d 44 12 28 01 00 75 90 48 c7 c7 20 19 2f 82 c6 05 34 12 28 01 01 e8 27 ca c0 ff <0f> 0b c3 80 3d 23 12 28 01 00 0f 85 6d ff ff ff 48 c7 c7 78 19 2f
[30843.780861] RSP: 0018:ffffc90000fa7d08 EFLAGS: 00010286
[30843.780863] RAX: 0000000000000000 RBX: 0000000000000004 RCX: 0000000000000007
[30843.780864] RDX: 0000000000000000 RSI: 0000000000000082 RDI: ffff88840bd19c10
[30843.780865] RBP: 000000000000000a R08: 000000000000051e R09: 0000000000000001
[30843.780867] R10: 0000000000000000 R11: 0000000000000001 R12: ffff88829de70c00
[30843.780868] R13: ffff8884056c8000 R14: ffffc90000fa7e08 R15: ffffffffa0278ea0
[30843.780870] FS: 00007f1028a6f940(0000) GS:ffff88840bd00000(0000) knlGS:0000000000000000
[30843.780872] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[30843.780873] CR2: 00003b1f0b8b9000 CR3: 00000003bda2c000 CR4: 00000000000006e0
[30843.780874] Call Trace:
[30843.780914] nouveau_gem_new+0x10b/0x120 [nouveau]
[30843.780944] ? nouveau_gem_new+0x120/0x120 [nouveau]
[30843.780968] nouveau_gem_ioctl_new+0x4e/0xc0 [nouveau]
[30843.780984] drm_ioctl_kernel+0xa7/0xf0 [drm]
[30843.780997] drm_ioctl+0x1f3/0x3b0 [drm]
[30843.781026] ? nouveau_gem_new+0x120/0x120 [nouveau]
[30843.781056] nouveau_drm_ioctl+0x60/0x15b0 [nouveau]
[30843.781061] ksys_ioctl+0x81/0xc0
[30843.781064] __x64_sys_ioctl+0x11/0x20
[30843.781068] do_syscall_64+0x4d/0x190
[30843.781071] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[30843.781074] RIP: 0033:0x7f1029117667
[30843.781076] Code: 00 00 00 75 0c 48 c7 c0 ff ff ff ff 48 83 c4 18 c3 e8 ed c0 01 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d f9 17 0d 00 f7 d8 64 89 01 48
[30843.781077] RSP: 002b:00007ffe96357758 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[30843.781080] RAX: ffffffffffffffda RBX: 0000562c53b92c80 RCX: 00007f1029117667
[30843.781081] RDX: 00007ffe963577b0 RSI: 00000000c0306480 RDI: 000000000000000c
[30843.781083] RBP: 00007ffe963577b0 R08: 0000000000000000 R09: 000000000000000c
[30843.781084] R10: 0000000000000030 R11: 0000000000000246 R12: 00000000c0306480
[30843.781085] R13: 000000000000000c R14: 0000562c528d4220 R15: 0000562c520cf1b0
[30843.781089] ---[ end trace 0f65c5f7ebdc9bbd ]---
[33664.882517] [TTM] Buffer eviction failed
```
```
# lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation G92GLM [Quadro FX 2800M] (rev a2)
# uname -a
Linux ironlight2 5.6.0-sabayon #1 SMP Tue Jun 23 13:11:32 UTC 2020 x86_64 Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz GenuineIntel GNU/Linux
```
What I saw is that seems happens more frequently when the RAM has less free memory or when I use Libreoffice (maybe for the same reason).
It seems maybe related to this: https://bugzilla.redhat.com/show_bug.cgi?id=1806239https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/5423d frame-packing mode not supported in X112022-01-23T00:48:31Zmax maier3d frame-packing mode not supported in X11Sorry, if its a foolish question - i'm not a Linux-pro...
I would like to give out a video stream in frame-packing mode to a 3d capable projector. But it seems impossible, because X11 can not handle this mode.
Thats at least what Kodi de...Sorry, if its a foolish question - i'm not a Linux-pro...
I would like to give out a video stream in frame-packing mode to a 3d capable projector. But it seems impossible, because X11 can not handle this mode.
Thats at least what Kodi devs told me, is the reason for the lack of 3d-possibilities in Linux.
So is there a reason for excluding this common 3d-protocol or was it somehow forgotten?
The frame-packing mode was introduced in the HDMI protocol more than 10 years ago.
And is there maybe a way to access the frame-packing mode which is hard to find?https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/541When using GT730, the screen collapses and freezes while loading the initial ...2020-07-30T11:51:38ZnexryaiWhen using GT730, the screen collapses and freezes while loading the initial RAM disk. (Arch Linux)When using an nvidia graphics board (palit GT730), the screen collapses during the loading of the initial ram disk in the environment immediately after installation and will not boot...
![88817938-19e94000-d1f9-11ea-941c-a5fa7bf7cca2](...When using an nvidia graphics board (palit GT730), the screen collapses during the loading of the initial ram disk in the environment immediately after installation and will not boot...
![88817938-19e94000-d1f9-11ea-941c-a5fa7bf7cca2](/uploads/332839e3eca5a498266000deb5aaaa7e/88817938-19e94000-d1f9-11ea-941c-a5fa7bf7cca2.jpg)
environment
dell optiplex790 i7-2600
Graphics : Palit nvidia GT730 GDDR5 1024MB (https://www.palit.com/palit/vgapro.php?id=2343&lang=jp)
OS : Arch Linux-based Alter linux beta3.1
Drivers used : xf86-video-nouveau
Switching to another graphics board (512MB AMD RADEON HD 6350 or Intel integrated graphics) will work fine. Also, nvidia graphics boards seem to work fine in a live environment.https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/540Unable to suspend TU116M (GF 1660 Ti) - regression in 5.7.6+ (nouveau 0000:01...2020-08-18T19:11:12ZMarcin ZajączkowskiUnable to suspend TU116M (GF 1660 Ti) - regression in 5.7.6+ (nouveau 0000:01:00.0: acr: init failed, -110)In kernel 5.7.6+ (tested up to 5.7.10 and 5.8.0-0.rc6.20200723gitd15be546031c - in 5.7.5 it worked fine) it is no longer possible to suspend Hyperbook NH5/Clevo NH55RCQ with GeForce GTX 1660 Mobile (TU116M):
```
kernel: Freezing remaini...In kernel 5.7.6+ (tested up to 5.7.10 and 5.8.0-0.rc6.20200723gitd15be546031c - in 5.7.5 it worked fine) it is no longer possible to suspend Hyperbook NH5/Clevo NH55RCQ with GeForce GTX 1660 Mobile (TU116M):
```
kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
kernel: printk: Suspending console(s) (use no_console_suspend to debug)
↓ related errrors ↓
kernel: xhci_hcd 0000:01:00.2: WARN: xHC CMD_RUN timeout
kernel: PM: suspend_common(): xhci_pci_suspend+0x0/0x100 returns -110
kernel: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110
kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -110
kernel: PM: Device 0000:01:00.2 failed to suspend async: error -110
↑ related errrors ↑
kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
kernel: sd 4:0:0:0: [sda] Stopping disk
kernel: PM: Some devices failed to suspend, or early wake event detected
kernel: sd 4:0:0:0: [sda] Starting disk
kernel: PM: resume devices took 2.184 seconds
kernel: OOM killer enabled.
kernel: Restarting tasks ... done.
kernel: PM: suspend exit
...
systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Suspend.
systemd[1]: Dependency failed for Suspend.
systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
systemd[1]: Stopped target Sleep.
```
The suspend process is aborted and the system stays as is (still can be used, once the screen is unlocked).
`01:00.2` is the NVidia's USB host:
```
$ lspci | grep -i nvidia 15:38
01:00.0 VGA compatible controller: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU116 USB 3.1 Host Controller (rev a1)
01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 USB Type-C UCSI Controller (rev a1)
```
The change is most likely not in the nouveau driver itself, but definitely impacts it. During the system boot the following error and stack trace is visible in the system log (new in 5.7.6):
```
Jul 29 15:11:13 hszpak kernel: fb0: switching to inteldrmfb from EFI VGA
Jul 29 15:11:13 hszpak kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Jul 29 15:11:13 hszpak kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Jul 29 15:11:13 hszpak kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Jul 29 15:11:13 hszpak kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
Jul 29 15:11:13 hszpak kernel: MXM: GUID detected in BIOS
Jul 29 15:11:13 hszpak kernel: ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20200326/nsarguments-59)
Jul 29 15:11:13 hszpak kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20200326/nsarguments-59)
Jul 29 15:11:13 hszpak kernel: pci 0000:01:00.0: optimus capabilities: enabled, status dynamic power, hda bios codec supported
Jul 29 15:11:13 hszpak kernel: VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG0.PEGP handle
Jul 29 15:11:13 hszpak kernel: nouveau: detected PR support, will not use DSM
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: enabling device (0106 -> 0107)
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: NVIDIA TU116 (168000a1)
Jul 29 15:11:13 hszpak kernel: [drm] Initialized i915 1.6.0 20200313 for 0000:00:02.0 on minor 0
Jul 29 15:11:13 hszpak kernel: ACPI: Video Device [PEGP] (multi-head: no rom: yes post: no)
Jul 29 15:11:13 hszpak kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input25
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: bios: version 90.16.26.00.11
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: fb: 6144 MiB GDDR6
Jul 29 15:11:13 hszpak kernel: input: Logitech Wireless Mouse PID:101f Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C52F.0002/0003:046D:101F.0006/input/input21
Jul 29 15:11:13 hszpak kernel: hid-generic 0003:046D:101F.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech Wireless Mouse PID:101f] on usb-0000:00:14.0-1/input1:1
Jul 29 15:11:13 hszpak kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
Jul 29 15:11:13 hszpak kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input26
Jul 29 15:11:13 hszpak kernel: input: SYNA1202:00 06CB:CD65 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-SYNA1202:00/0018:06CB:CD65.0005/input/input27
Jul 29 15:11:13 hszpak kernel: input: SYNA1202:00 06CB:CD65 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-SYNA1202:00/0018:06CB:CD65.0005/input/input28
Jul 29 15:11:13 hszpak kernel: vga_switcheroo: enabled
Jul 29 15:11:13 hszpak kernel: [TTM] Zone kernel: Available graphics memory: 8046730 KiB
Jul 29 15:11:13 hszpak kernel: [TTM] Zone dma32: Available graphics memory: 2097152 KiB
Jul 29 15:11:13 hszpak kernel: [TTM] Initializing pool allocator
Jul 29 15:11:13 hszpak kernel: [TTM] Initializing DMA pool allocator
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: VRAM: 6144 MiB
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: GART: 536870912 MiB
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: BIT table 'A' not found
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: BIT table 'L' not found
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: TMDS table version 2.0
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB version 4.1
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB outp 00: 02002f52 00020010
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB outp 01: 04814f76 04600010
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB outp 02: 04814f72 00020010
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB conn 02: 00010261
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB conn 04: 01000446
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
Jul 29 15:11:13 hszpak kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
Jul 29 15:11:13 hszpak kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: Disabling PCI power management to avoid bug
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
Jul 29 15:11:13 hszpak kernel: hid-multitouch 0018:06CB:CD65.0005: input,hidraw3: I2C HID v1.00 Mouse [SYNA1202:00 06CB:CD65] on i2c-SYNA1202:00
Jul 29 15:11:13 hszpak kernel: psmouse serio2: synaptics: device claims to have extended capability 0x0c, but I'm not able to read it.
Jul 29 15:11:13 hszpak kernel: fbcon: i915drmfb (fb0) is primary device
Jul 29 15:11:13 hszpak kernel: fbcon: Deferring console take-over
Jul 29 15:11:13 hszpak kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
Jul 29 15:11:13 hszpak kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
Jul 29 15:11:13 hszpak kernel: psmouse serio2: synaptics: Unable to initialize device.
Jul 29 15:11:18 hszpak kernel: input: Logitech Wireless Mouse PID:101f as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C52F.0002/0003:046D:101F.0006/input/input30
Jul 29 15:11:18 hszpak kernel: logitech-hidpp-device 0003:046D:101F.0006: input,hidraw5: USB HID v1.11 Mouse [Logitech Wireless Mouse PID:101f] on usb-0000:00:14.0-1/input1:1
Jul 29 15:11:18 hszpak kernel: input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input14
Jul 29 15:11:19 hszpak kernel: psmouse serio2: Failed to enable mouse on isa0060/serio2
↓ new in 5.7.6 ↓
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: fifo: fault 09 [PHYS_WRITE] at 000000017fef0000 engine c0 [BAR2] client 08 [HUB/HOST_CPU_NB] reason 0d [REGION_VIOLATION] on channel -1 [0000000000 unknown]
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: fifo: fault 09 [PHYS_WRITE] at 000000017fef0000 engine c0 [BAR2] client 08 [HUB/HOST_CPU_NB] reason 0d [REGION_VIOLATION] on channel -1 [0000000000 unknown]
Jul 29 15:11:21 hszpak kernel: ------------[ cut here ]------------
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: timeout
Jul 29 15:11:21 hszpak kernel: WARNING: CPU: 4 PID: 428 at drivers/gpu/drm/nouveau/nvkm/falcon/v1.c:247 nvkm_falcon_v1_wait_for_halt+0x96/0xa0 [nouveau]
Jul 29 15:11:21 hszpak kernel: Modules linked in: hid_logitech_hidpp i915 nouveau hid_multitouch ttm cec rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper mmc_core mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel nvme drm nvme_core ghash_clmu>
Jul 29 15:11:21 hszpak kernel: CPU: 4 PID: 428 Comm: plymouthd Not tainted 5.7.6-201.fc32.x86_64 #1
Jul 29 15:11:21 hszpak kernel: Hardware name: Blue Technology Sp. z o.o. NH5_NH7/NH5_NH7, BIOS 1.07.03TBT 11/16/2018
Jul 29 15:11:21 hszpak kernel: RIP: 0010:nvkm_falcon_v1_wait_for_halt+0x96/0xa0 [nouveau]
Jul 29 15:11:21 hszpak kernel: Code: 8b 40 10 48 8b 78 10 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 1c aa 03 d6 4c 89 e2 48 c7 c7 8c d2 86 c0 48 89 c6 e8 31 56 a3 d5 <0f> 0b eb ba 66 0f 1f 44 00 00 0f 1f 44 00 00 41 54 be 80 96 98 00
Jul 29 15:11:21 hszpak kernel: RSP: 0018:ffffb44840707838 EFLAGS: 00010292
Jul 29 15:11:21 hszpak kernel: RAX: 000000000000001d RBX: ffffffffffffff92 RCX: 0000000000000007
Jul 29 15:11:21 hszpak kernel: RDX: 00000000fffffff8 RSI: 0000000000000092 RDI: ffff8f0b60519cc0
Jul 29 15:11:21 hszpak kernel: RBP: ffff8f0b518cb658 R08: 0000000000000385 R09: 0000000000000003
Jul 29 15:11:21 hszpak kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff8f0b5d738020
Jul 29 15:11:21 hszpak kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff8f0b5441a000
Jul 29 15:11:21 hszpak kernel: FS: 00007ff013b2cf00(0000) GS:ffff8f0b60500000(0000) knlGS:0000000000000000
Jul 29 15:11:21 hszpak kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 29 15:11:21 hszpak kernel: CR2: 000055b4f79f9198 CR3: 000000045471c006 CR4: 00000000003606e0
Jul 29 15:11:21 hszpak kernel: Call Trace:
Jul 29 15:11:21 hszpak kernel: gm200_acr_hsfw_boot+0xc3/0x160 [nouveau]
Jul 29 15:11:21 hszpak kernel: ? mutex_lock+0xe/0x30
Jul 29 15:11:21 hszpak kernel: nvkm_acr_hsf_boot+0x85/0xe0 [nouveau]
Jul 29 15:11:21 hszpak kernel: tu102_acr_init+0x15/0x30 [nouveau]
Jul 29 15:11:21 hszpak kernel: nvkm_acr_load+0x2b/0xd0 [nouveau]
Jul 29 15:11:21 hszpak kernel: ? ktime_get+0x38/0x90
Jul 29 15:11:21 hszpak kernel: nvkm_subdev_init+0x92/0xd0 [nouveau]
Jul 29 15:11:21 hszpak kernel: ? ktime_get+0x38/0x90
Jul 29 15:11:21 hszpak kernel: nvkm_device_init+0x10b/0x190 [nouveau]
Jul 29 15:11:21 hszpak kernel: nvkm_udevice_init+0x41/0x60 [nouveau]
Jul 29 15:11:21 hszpak kernel: nvkm_object_init+0x3e/0x100 [nouveau]
Jul 29 15:11:21 hszpak kernel: nvkm_object_init+0x6f/0x100 [nouveau]
Jul 29 15:11:21 hszpak kernel: nvkm_object_init+0x6f/0x100 [nouveau]
Jul 29 15:11:21 hszpak kernel: nouveau_do_resume+0x2a/0xc0 [nouveau]
Jul 29 15:11:21 hszpak kernel: nouveau_pmops_runtime_resume+0x7a/0x170 [nouveau]
Jul 29 15:11:21 hszpak kernel: pci_pm_runtime_resume+0xaa/0xc0
Jul 29 15:11:21 hszpak kernel: ? pci_pm_freeze_noirq+0x110/0x110
Jul 29 15:11:21 hszpak kernel: __rpm_callback+0x81/0x140
Jul 29 15:11:21 hszpak kernel: ? pci_pm_freeze_noirq+0x110/0x110
Jul 29 15:11:21 hszpak kernel: rpm_callback+0x1f/0x70
Jul 29 15:11:21 hszpak kernel: ? pci_pm_freeze_noirq+0x110/0x110
Jul 29 15:11:21 hszpak kernel: rpm_resume+0x575/0x7c0
Jul 29 15:11:21 hszpak kernel: ? __mod_lruvec_state+0x44/0xf0
Jul 29 15:11:21 hszpak kernel: __pm_runtime_resume+0x4a/0x80
Jul 29 15:11:21 hszpak kernel: nouveau_drm_open+0x3b/0x1a0 [nouveau]
Jul 29 15:11:21 hszpak kernel: ? security_capable+0x36/0x50
Jul 29 15:11:21 hszpak kernel: drm_file_alloc+0x194/0x250 [drm]
Jul 29 15:11:21 hszpak kernel: drm_open+0xce/0x250 [drm]
Jul 29 15:11:21 hszpak kernel: drm_stub_open+0xad/0x140 [drm]
Jul 29 15:11:21 hszpak kernel: chrdev_open+0xdd/0x210
Jul 29 15:11:21 hszpak kernel: ? cdev_device_add+0xc0/0xc0
Jul 29 15:11:21 hszpak kernel: do_dentry_open+0x13a/0x380
Jul 29 15:11:21 hszpak kernel: path_openat+0xa9a/0xfe0
Jul 29 15:11:21 hszpak kernel: ? current_time+0x1b/0xd0
Jul 29 15:11:21 hszpak kernel: ? atime_needs_update+0x73/0xd0
Jul 29 15:11:21 hszpak kernel: do_filp_open+0x75/0x100
Jul 29 15:11:21 hszpak kernel: ? __check_object_size+0x12e/0x13c
Jul 29 15:11:21 hszpak kernel: ? __alloc_fd+0x44/0x150
Jul 29 15:11:21 hszpak kernel: do_sys_openat2+0x8a/0x130
Jul 29 15:11:21 hszpak kernel: __x64_sys_openat+0x46/0x70
Jul 29 15:11:21 hszpak kernel: do_syscall_64+0x5b/0xf0
Jul 29 15:11:21 hszpak kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jul 29 15:11:21 hszpak kernel: RIP: 0033:0x7ff013de414b
Jul 29 15:11:21 hszpak kernel: Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 48 8b 4c 24 28 64 48 33 0c 25
Jul 29 15:11:21 hszpak kernel: RSP: 002b:00007ffd4536a520 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
Jul 29 15:11:21 hszpak kernel: RAX: ffffffffffffffda RBX: 00007ff013b2ce80 RCX: 00007ff013de414b
Jul 29 15:11:21 hszpak kernel: RDX: 0000000000000002 RSI: 000055b4f79e54c0 RDI: 00000000ffffff9c
Jul 29 15:11:21 hszpak kernel: RBP: 000055b4f79e54c0 R08: 000055b4f79e5400 R09: 00007ff013efc380
Jul 29 15:11:21 hszpak kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
Jul 29 15:11:21 hszpak kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Jul 29 15:11:21 hszpak kernel: ---[ end trace 71e1c4626a3ab07b ]---
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: acr: AHESASC binary failed
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: acr: init failed, -110
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: init failed with -110
Jul 29 15:11:21 hszpak kernel: nouveau: systemd-udevd[445]:00000000:00000080: init failed with -110
Jul 29 15:11:21 hszpak kernel: nouveau: DRM-master:00000000:00000000: init failed with -110
Jul 29 15:11:21 hszpak kernel: nouveau: DRM-master:00000000:00000000: init failed with -110
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: DRM: Client resume failed with error: -110
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: DRM: resume failed with: -110
↑ new in 5.7.6 ↑
```
As it was introduced between the minor kernel version, number of commits is smaller than between the major ones. Maybe someone with bigger nouveau/drm experience could suggest what could be the culprit to consult it with the commit author?
https://lwn.net/Articles/824499/
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.7.6
Btw, there was a similar in effects [regression in 5.3](https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/516#note_388553), but it was fixed in 5.5.0-rc2+.https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/17debian/sid: amdgpu crash on undock2023-07-12T20:32:12ZTim Foersterdebian/sid: amdgpu crash on undockI currently trigger the following backtrace on my T495 always on undocking. The crash only happens with opened lid.
```
[108137.178] (II) AMDGPU(0): EDID vendor "AUO", prod id 22333
[108137.179] (II) AMDGPU(0): Printing DDC gathered Mod...I currently trigger the following backtrace on my T495 always on undocking. The crash only happens with opened lid.
```
[108137.178] (II) AMDGPU(0): EDID vendor "AUO", prod id 22333
[108137.179] (II) AMDGPU(0): Printing DDC gathered Modelines:
[108137.179] (II) AMDGPU(0): Modeline "1920x1080"x0.0 142.60 1920 1936 1952 2080 1080 1083 1088 1142 -hsync -vsync (68.6 kHz eP)
[108137.199] (II) AMDGPU(0): EDID vendor "AUO", prod id 22333
[108137.199] (II) AMDGPU(0): Printing DDC gathered Modelines:
[108137.199] (II) AMDGPU(0): Modeline "1920x1080"x0.0 142.60 1920 1936 1952 2080 1080 1083 1088 1142 -hsync -vsync (68.6 kHz eP)
[108137.339] (EE)
[108137.339] (EE) Backtrace:
[108137.340] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x138) [0x5587e6e21e88]
[108137.344] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fdb068bd15f]
[108137.346] (EE) unw_get_proc_name failed: no unwind info found [-10]
[108137.347] (EE) 2: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7fdb05e5aff0]
[108137.348] (EE) unw_get_proc_name failed: no unwind info found [-10]
[108137.348] (EE) 3: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7fdb05e5b290]
[108137.349] (EE) 4: /usr/lib/xorg/Xorg (xf86DPMSSet+0x63) [0x5587e6d33db3]
[108137.350] (EE) 5: /usr/lib/xorg/Xorg (xf86SetDGAMode+0x886) [0x5587e6d01b06]
[108137.350] (EE) 6: /usr/lib/xorg/Xorg (XaceIsLocal+0x5b16) [0x5587e6d7ac86]
[108137.351] (EE) 7: /usr/lib/xorg/Xorg (mieqProcessInputEvents+0x165) [0x5587e6e01b95]
[108137.352] (EE) 8: /usr/lib/xorg/Xorg (ProcessInputEvents+0x19) [0x5587e6d015f9]
[108137.352] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x2c9) [0x5587e6cc48d9]
[108137.353] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5587e6cc8914]
[108137.356] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fdb0670ae0b]
[108137.356] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2a) [0x5587e6cb273a]
[108137.356] (EE)
[108137.356] (EE) Segmentation fault at address 0x0
[108137.356] (EE)
Fatal server error:
[108137.356] (EE) Caught signal 11 (Segmentation fault). Server aborting
[108137.357] (EE)
[108137.357] (EE)
```
```
xserver-xorg-core:
Installed: 2:1.20.8-2
xserver-xorg-video-amdgpu:
Installed: 19.1.0-1
```
```
>>> uname -a
Linux tonobo-top 5.7.0-1-amd64 #1 SMP Debian 5.7.6-1 (2020-06-24) x86_64 GNU/Linux
```
[Xorg.0.log.old](/uploads/70b453e1340e778578e31c0506c5b497/Xorg.0.log.old)https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/-/issues/201Possible lack in documentation: Option "AccelMethod" "string" on i915 kernel ...2020-07-23T05:16:42ZGhost UserPossible lack in documentation: Option "AccelMethod" "string" on i915 kernel module**Targeting lack area**
On the https://jlk.fjfi.cvut.cz/arch/manpages/man/intel.4 page there is the section
`The following driver Options are supported for the 830M and later chipsets:`
and
`Option "Accel" "boolean"`,
`Option "Accel...**Targeting lack area**
On the https://jlk.fjfi.cvut.cz/arch/manpages/man/intel.4 page there is the section
`The following driver Options are supported for the 830M and later chipsets:`
and
`Option "Accel" "boolean"`,
`Option "AccelMethod" "string"`
in it.
**Experiment**
I tried to use
`Option "Accel" "false"`
and saw certain visual defects I never saw before.
Than *instead* of the option above I tried
`Option "AccelMethod" "none"`
and saw the same certain visual defects which I saw was with Option `"Accel" "false"`.
***1 fix)***
If it is true by actual driver API, may be will be good to clarify by mention in doc what both parameters-values lines has the same effect?
Then instead of all above lines I tried
`Option "AccelMethod" "off"`
but I saw no certain visual effects as was with `"none"` value
***2 fix)*** If it is true by actual driver API, than `"off"` value is fake/obsolete/non-working.
Thank you for your work!
-------
Looks like I have i915 kernel module (you can see it my bug reports in another project: https://gitlab.freedesktop.org/drm/intel/-/issues/2187 )
CPU is Intel Core i5-8250U with Intel UHD Graphics 620 GPU on-die as the only GPU in the system.
( https://ark.intel.com/content/www/us/en/ark/products/124967/intel-core-i5-8250u-processor-6m-cache-up-to-3-40-ghz.html )https://gitlab.freedesktop.org/xorg/driver/xf86-video-tseng/-/issues/2Broken struct2022-01-30T20:12:53ZRobert BrownBroken struct@see this commit - https://gitlab.freedesktop.org/xorg/xserver/-/commit/5a945f54e738f6e9c5a489febdd8b87cd8a41210
It remmoved maxHValue and maxVValue from struct _ScrnInfoRec in the xf86str.h include file. The primary driver file in this...@see this commit - https://gitlab.freedesktop.org/xorg/xserver/-/commit/5a945f54e738f6e9c5a489febdd8b87cd8a41210
It remmoved maxHValue and maxVValue from struct _ScrnInfoRec in the xf86str.h include file. The primary driver file in this repo, tseng_drivers.c, still references those values and fails to compile.
I created a simple patch to remove those values and instead use the already-set versions of them. That allows it to build.
[tseng.patch](/uploads/b62b698e2ab0d18af7b181f8f384feb8/tseng.patch)
I'm relatively clueless as to how this bit of code works or the implications but I'll test and report back. I intentionally did not submit a merge, a code review here would be needed given my rusty dev skills.https://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/-/issues/11Two-finger scrolling randomly triggers a click.2020-07-16T06:17:47ZRodrigo Pelissierpelirodri@icloud.comTwo-finger scrolling randomly triggers a click.When scrolling on my 2014 MacBook Pro with tap to click enabled, the things I scroll over get randomly clicked all the time and it is extremely annoying and inconvenient. As soon as I touch the trackpad with two fingers while the cursor ...When scrolling on my 2014 MacBook Pro with tap to click enabled, the things I scroll over get randomly clicked all the time and it is extremely annoying and inconvenient. As soon as I touch the trackpad with two fingers while the cursor is over some clickable element, that element gets clicked sometimes.
I observed that while the sequence of tap states for successful attempts was `TS_1` -> `TS_MOVE`, the sequence of tap states for unsuccessful attempts was `TS_1` -> `TS_2A` -> `TS_3`, and also, the pressure returned by the input event (`ABS_PRESSURE`) before `TS_2A` gets set is 0, which means the first finger is treated as if it were released before recognizing the second finger as a second touch. This happens even though no finger was ever released and it seems to occur at random, maybe more often when the second finger is placed on the trackpad a few milliseconds later than the first one.https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/539[NV98] Lots of screen freezes2021-08-25T06:22:05ZH. ROMANO[NV98] Lots of screen freezesI'm experiencing more and more screen freezes related to nouveau (two or three everyday at least). Most of the time, I can ssh and reboot, but it's getting really annoying.
Here is the latest dmesg, this time a hard reboot was needed (...I'm experiencing more and more screen freezes related to nouveau (two or three everyday at least). Most of the time, I can ssh and reboot, but it's getting really annoying.
Here is the latest dmesg, this time a hard reboot was needed (a reboot over ssh hung).
[crash.log](/uploads/3a5d28c3bc80b3b31138b6eda7d38c29/crash.log)