Created attachment 1479206 [details] journal file Description of problem: Random system freeze using Gnome with wayland and nouveau. ctrl-alt-f3 sysrq keys, ctrl-alt-del, nothing helps, only hard reset. I have not tried to ssh in though (no ssh server installed) It may be when moving the mouse as in 1514831 I am not sure if it's a Nouveau bug, or a Wayland bug, but switching to a Xorg/Gnome sessions stops the freeze thing. May be duplicate of bug 1509294, 1435000, 1529854 or 1514831 but none of those really seem to match my issue, and one is closed. My graphics card is GT 550 Ti Version-Release number of selected component (if applicable): Nom : xorg-x11-drv-nouveau Époque : 1 Version : 1.0.15 Révision : 4.fc28 Nom : xorg-x11-server-Xwayland Version : 1.19.6 Révision : 8.fc28 kernel : 4.17.17-200.fc28.x86_64 How reproducible: randomly. Steps to Reproduce: 1.Start a Gnome/Wayland session 2.just do things, after a random time, system freezes. 3.hard reset... Actual results:system random freeze Expected results:no freeze Additional info: log from journactl attached. extract : août 26 00:32:51 localhost.localdomain gdm[750]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed août 26 15:30:00 localhost.localdomain gdm[756]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed août 26 19:09:42 localhost.localdomain kernel: nouveau 0000:01:00.0: Xwayland[1727]: nv50cal_space: -16 (message repeated hundreds of times and then :) août 26 19:10:01 localhost.localdomain systemd-journald[415]: Suppressed 4593 messages from session-4.scope ... Nothing more then hard-reset. Workaround : Start a Gnome/Xorg session.
Created attachment 1479220 [details] User journal file Due to another problem with system clock, I had incoherent timestamps and could not analyze logs with journalctl. So the files attached are generated with journalctl --file <files of time machine crashed> >file.log I upload now the user log containing interesting entries too such as : août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: 0x20046234 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: 0x00000000 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: kernel rejected pushbuf: Device or resource busy août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: ch13: krec 0 pushes 1 bufs 6 relocs 0 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: ch13: buf 00000000 00000002 00000004 00000004 00000000 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: ch13: buf 00000001 00000006 00000004 00000000 00000004 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: ch13: buf 00000002 00000018 00000002 00000000 00000002 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: ch13: buf 00000003 00000015 00000004 00000004 00000000 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: ch13: buf 00000004 0000001c 00000004 00000004 00000000 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: ch13: buf 00000005 0000001d 00000004 00000004 00000000 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: ch13: psh 00000000 0000018bc8 0000018d78 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: 0x20056080 août 26 19:10:02 localhost.localdomain org.gnome.Shell.desktop[1674]: nouveau: 0x000000e6
Created attachment 1480160 [details] dmesg during freeze
Created attachment 1480161 [details] journalctl at moment of freeze. Freeze occurred at 09:44
New info : I was able to ssh in during a desktop freeze (even though any combination of keys would not work from keyboard) Attached logs from that moment. Freeze occurred at 09:44. extract of dmesg : [ 2737.189962] WARNING: CPU: 1 PID: 5238 at drivers/gpu/drm/nouveau/nouveau_bo.c:1288 nouveau_bo_move_ntfy+0xa9/0xd0 [nouveau] [ 2737.189964] Modules linked in: fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack devlink ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables sunrpc snd_hda_codec_hdmi edac_mce_amd kvm_amd ccp kvm snd_hda_codec_realtek snd_hda_codec_generic irqbypass snd_hda_intel snd_hda_codec snd_hda_core k10temp snd_hwdep snd_seq snd_seq_device sp5100_tco snd_pcm i2c_piix4 snd_timer snd soundcore shpchp pcc_cpufreq [ 2737.189988] acpi_cpufreq ata_generic pata_acpi r8169 serio_raw mii pata_atiixp nouveau video mxm_wmi wmi i2c_algo_bit drm_kms_helper ttm drm [ 2737.189996] CPU: 1 PID: 5238 Comm: kworker/u16:4 Tainted: G W 4.17.18-200.fc28.x86_64 #1 [ 2737.189996] Hardware name: MSI MS-7693/970A-G46 (MS-7693), BIOS V1.11 10/31/2012 [ 2737.190003] Workqueue: ttm_swap ttm_shrink_work [ttm] [ 2737.190033] RIP: 0010:nouveau_bo_move_ntfy+0xa9/0xd0 [nouveau] [ 2737.190034] RSP: 0018:ffffb65186d23cc0 EFLAGS: 00010286 [ 2737.190035] RAX: 00000000fffffff0 RBX: ffff9f93e292d940 RCX: 0000000000000000 [ 2737.190036] RDX: 0000000000000000 RSI: 0000000000000296 RDI: 0000000000000296 [ 2737.190037] RBP: ffff9f93cace5000 R08: ffff9f942fc616e0 R09: 0000000000000000 [ 2737.190037] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9f93cace52e8 [ 2737.190038] R13: 0000000000000000 R14: ffffb65186d23d98 R15: 0000000000000000 [ 2737.190039] FS: 0000000000000000(0000) GS:ffff9f942fc40000(0000) knlGS:0000000000000000 [ 2737.190040] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2737.190040] CR2: 00007f7e9b01e000 CR3: 0000000186e52000 CR4: 00000000000006e0 [ 2737.190042] Call Trace: [ 2737.190051] ttm_bo_handle_move_mem+0xc0/0x530 [ttm] [ 2737.190055] ttm_bo_swapout+0x20c/0x2b0 [ttm] [ 2737.190082] ? drm_vma_offset_lookup_locked+0x10/0x60 [drm] [ 2737.190086] ttm_shrink+0x9a/0xc0 [ttm] [ 2737.190090] ttm_shrink_work+0x4f/0x70 [ttm] [ 2737.190098] process_one_work+0x187/0x340 [ 2737.190101] worker_thread+0x2e/0x380 [ 2737.190103] ? pwq_unbound_release_workfn+0xd0/0xd0 [ 2737.190105] kthread+0x112/0x130 [ 2737.190107] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2737.190112] ret_from_fork+0x22/0x40 [ 2737.190114] Code: a4 31 d2 31 f6 48 89 ef e8 95 1d ee ff 85 c0 75 1a 48 89 df e8 59 72 00 00 48 8b 43 10 48 8d 58 f0 49 39 c4 75 db e9 7a ff ff ff <0f> 0b eb e2 48 3d 10 79 5d c0 0f 85 6a ff ff ff 48 8b 87 e8 02 [ 2737.190133] ---[ end trace 4ee1ac81c5b9516d ]---
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.