I think my modeset=1 test earlier was invalid; I don't think that change was ever applied. It *did* get applied just now with a routine dist- upgrade, which included an update to console-setup, which forced update- initramfs. And then the system was unbootable except via the recovery system. syslog is full of crashes like this in rapid succession:
Sep 30 13:33:38 fleetfoot kernel: [ 117.641448] ------------[ cut here ]------------ Sep 30 13:33:38 fleetfoot kernel: [ 117.641467] WARNING: CPU: 0 PID: 221 at /build/linux-s_bACt/linux-4.13.0/drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_commit_hw_done+0x99/0xa0 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641468] Modules linked in: rfcomm hid_magicmouse hidp cmac bnep nls_iso8859_1 nvidia_uvm(POE) hid_apple joydev input_leds hid_generic ath3k btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib usbhid hid ecdh_generic snd_hda_codec_hdmi eeepc_wmi asus_wmi cmdlinepart intel_spi_platform intel_rapl intel_spi spi_nor wmi_bmof sparse_keymap mtd x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm snd_hda_codec_realtek snd_hda_codec_generic irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec pcbc snd_hda_core snd_hwdep arc4 snd_pcm snd_seq_midi ath9k aesni_intel snd_seq_midi_event ath9k_common ath9k_hw snd_rawmidi aes_x86_64 crypto_simd snd_seq glue_helper cryptd ath intel_cstate snd_seq_device intel_rapl_perf mac80211 snd_timer cfg80211 snd soundcore Sep 30 13:33:38 fleetfoot kernel: [ 117.641496] mei_me mei shpchp lpc_ich wmi mac_hid nct6775 hwmon_vid coretemp parport_pc ppdev lp parport ip_tables x_tables autofs4 nvidia_drm(POE) nvidia_modeset(POE) i915 nvidia(POE) i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ahci ptp drm libahci pps_core video Sep 30 13:33:38 fleetfoot kernel: [ 117.641507] CPU: 0 PID: 221 Comm: kworker/u16:6 Tainted: P W OE 4.13.0-12-generic #13-Ubuntu Sep 30 13:33:38 fleetfoot kernel: [ 117.641507] Hardware name: ASUS All Series/Z87I-PRO, BIOS 1005 11/26/2014 Sep 30 13:33:38 fleetfoot kernel: [ 117.641511] Workqueue: events_unbound commit_work [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641512] task: ffff970a91cec5c0 task.stack: ffffb72901e5c000 Sep 30 13:33:38 fleetfoot kernel: [ 117.641515] RIP: 0010:drm_atomic_helper_commit_hw_done+0x99/0xa0 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641515] RSP: 0018:ffffb72901e5fdb8 EFLAGS: 00010286 Sep 30 13:33:38 fleetfoot kernel: [ 117.641516] RAX: ffff970a8ff8b008 RBX: 0000000000000004 RCX: ffff970a9ca0c000 Sep 30 13:33:38 fleetfoot kernel: [ 117.641516] RDX: ffff970a8dce1400 RSI: 0000000000000001 RDI: ffff970a93a56c08 Sep 30 13:33:38 fleetfoot kernel: [ 117.641517] RBP: ffffb72901e5fdd8 R08: ffff970aafa12398 R09: 0000000000000018 Sep 30 13:33:38 fleetfoot kernel: [ 117.641517] R10: ffffb72901e5fd88 R11: 0000000000000372 R12: 0000000000000001 Sep 30 13:33:38 fleetfoot kernel: [ 117.641518] R13: ffff970a97780b40 R14: ffff970a93a56c08 R15: ffff970a93a56c08 Sep 30 13:33:38 fleetfoot kernel: [ 117.641518] FS: 0000000000000000(0000) GS:ffff970aafa00000(0000) knlGS:0000000000000000 Sep 30 13:33:38 fleetfoot kernel: [ 117.641519] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 30 13:33:38 fleetfoot kernel: [ 117.641519] CR2: 00007fa55cd3a010 CR3: 00000003ff609000 CR4: 00000000001406f0 Sep 30 13:33:38 fleetfoot kernel: [ 117.641520] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Sep 30 13:33:38 fleetfoot kernel: [ 117.641520] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Sep 30 13:33:38 fleetfoot kernel: [ 117.641521] Call Trace: Sep 30 13:33:38 fleetfoot kernel: [ 117.641524] nvidia_drm_atomic_helper_commit_tail+0x10e/0x170 [nvidia_drm] Sep 30 13:33:38 fleetfoot kernel: [ 117.641527] commit_tail+0x3f/0x60 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641530] commit_work+0x12/0x20 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641532] process_one_work+0x1e7/0x410 Sep 30 13:33:38 fleetfoot kernel: [ 117.641533] worker_thread+0x4a/0x410 Sep 30 13:33:38 fleetfoot kernel: [ 117.641534] kthread+0x125/0x140 Sep 30 13:33:38 fleetfoot kernel: [ 117.641535] ? process_one_work+0x410/0x410 Sep 30 13:33:38 fleetfoot kernel: [ 117.641536] ? kthread_create_on_node+0x70/0x70 Sep 30 13:33:38 fleetfoot kernel: [ 117.641538] ret_from_fork+0x25/0x30 Sep 30 13:33:38 fleetfoot kernel: [ 117.641538] Code: 7d 30 e8 db b8 2c fa 48 89 df c6 07 00 0f 1f 40 00 49 8b 4e 08 41 83 c4 01 44 39 a1 38 03 00 00 7f 98 5b 41 5c 41 5d 41 5e 5d c3 <0f> ff eb c0 f3 c3 90 0f 1f 44 00 00 48 8b 4f 08 8b 81 38 03 00 Sep 30 13:33:38 fleetfoot kernel: [ 117.641552] ---[ end trace ab364b2a1fae43bb ]--- Sep 30 13:33:39 fleetfoot kernel: [ 117.974932] ------------[ cut here ]------------ However that's probably offtopic here, and just speaks to nvidia kms not being usable yet, which we already knew. It was presumably off in my earlier test, which (therefore unsurprisingly) showed no difference to the default setup. I'm back now to a system with Xorg, modeset=0, needs_root_rights=auto (by default), and the default shell theme (and Ambiance main theme). I'll see if in normal use *this* bug recurs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep Status in gnome-shell package in Ubuntu: Confirmed Bug description: The observable symptom is that if I go away and let the computer go either to display sleep or suspend, when I come back and try to wake it up again, I find myself, after sliding up the lock screen, at the gdm login screen. I'm logged out, and logging in gives me a fresh new session. Anything I had open in the previous session is lost. (I'm getting used to saving stuff before I step away from the computer!) The only trace I've been able to find is that in /var/log/syslog I see a line like: Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]: segfault at 2c ip 00007f6200e82434 sp 00007ffc46f981c8 error 4 in libmutter-1.so.0.0.0[7f6200de4000+140000] This happens at the time of attempted wake, not the time of going to sleep. It's preceded by a lot of activity from gdm-x-session that I'm not sure is indicating any error, just the process of waking up. I will attach a portion of syslog surrounding the whole event in the hope it helps. (In fact attaching the whole current syslog file - it has two such events occuring in it, first display sleep/wake at 09:02 this morning, and secondly (because I was experimenting) a suspend- wake at 14:38 this afternoon. This is only affecting Xorg sessions, and may possibly only be affecting where nvidia is in use, I'm not sure about that. But the fact it occurs on display wake alone, not needing the system itself to have suspended (I was trying suspend to see if it *avoided* the problem, which it doesn't), does point the finger in that direction I guess. But ultimately I'm guessing it's gnome-shell itself segfaulting that's causing the login session to end? Not observed on my Wayland system. This is not new as of the current version of gnome-shell but I think it is relatively recent. Now my hackintosh partition is wrecked by a failed upgrade to High Sierra I'm using my Linux system more in earnest than before, so I'm hitting this often enough for it to provoke a bug report (and much of the time, to just turn all auto suspend/display-sleep off and instead shut down the computer when I'm leaving it for any length of time). The ubuntu bug reporter is not picking this up by itself, so I presume a crash report of the sort that uses is not being saved. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 28 14:41:07 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-30 (59 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
