Created attachment 1397380 [details] Screenshot with artefacts Description of problem: With new kernel-4.15.3-300.fc27.x86_64 I got artefacts and freezes Version-Release number of selected component (if applicable): 4.15.3-300.fc27.x86_64 How reproducible: always Steps to Reproduce: 1. boot with kernel-4.15 2. launch opengl app (supertuxcat) 3. get artefacts and then freeze Actual results: artefacts and freezes Expected results: Additional info: Gnome3 wayland session 03:00.0 VGA compatible controller: NVIDIA Corporation C79 [GeForce 9300 / nForce 730i] (rev b1) dmesg: [ 142.652554] nouveau 0000:03:00.0: imem: OOM: 00100000 00001000 -28 [ 142.652790] nouveau 0000:03:00.0: gr: TRAP_M2MF 00000002 [IN] [ 142.652800] nouveau 0000:03:00.0: gr: TRAP_M2MF 00320151 206f1fc0 00000000 04000430 [ 142.652809] nouveau 0000:03:00.0: gr: 00200000 [] ch 1 [000fbb0000 DRM] subc 4 class 5039 mthd 0100 data 00000000 [ 142.652826] nouveau 0000:03:00.0: fb: trapped read at 00206f0000 on channel 1 [0fbb0000 DRM] engine 00 [PGRAPH] client 03 [DISPATCH] subclient 04 [M2M_IN] reason 00000002 [PAGE_NOT_PRESENT] [ 142.672336] nouveau 0000:03:00.0: imem: OOM: 00100000 00001000 -28 [ 142.672391] nouveau 0000:03:00.0: gr: TRAP_M2MF 00000002 [IN] [ 142.672396] nouveau 0000:03:00.0: gr: TRAP_M2MF 00320951 206f1fc0 00000000 04000000 [ 142.672401] nouveau 0000:03:00.0: gr: 00200000 [] ch 1 [000fbb0000 DRM] subc 4 class 5039 mthd 0100 data 00000000 [ 142.672412] nouveau 0000:03:00.0: fb: trapped read at 00206f0000 on channel 1 [0fbb0000 DRM] engine 00 [PGRAPH] client 03 [DISPATCH] subclient 04 [M2M_IN] reason 00000006 [NULL_DMAOBJ]
also here 01:00.0 VGA compatible controller: NVIDIA Corporation G98M [GeForce 9300M GS] (rev a1) [ 29.876760] nouveau 0000:01:00.0: DRM: EVO timeout
Problem reproduced in wayland only. xorg session works fine. In demesg repeats: [ 93.304949] nouveau 0000:03:00.0: imem: OOM: 00100000 00001000 -28
Let's have the graphics team take a look. You should also file a bug at bugzilla.freedesktop.org
(In reply to Laura Abbott from comment #3) > You should also file a bug at bugzilla.freedesktop.org filed: https://bugs.freedesktop.org/show_bug.cgi?id=105173
dnf -y update 24 Feb. Whole system slow / unresponsive. Unable to interrupt boot to revert to older kernel System now unusable as is
(In reply to Dave P from comment #5) > dnf -y update 24 Feb. > Whole system slow / unresponsive. > Unable to interrupt boot to revert to older kernel > > System now unusable as is Installed @KDE. Now a slow boot, but fine once KDE is running.
This patch https://github.com/skeggsb/nouveau/pull/1/files fixed my problem
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.