Uh, if anyone else is affected by this, there's a trivial fix upstream already (and a workaround). Hop to it, Ubuntu. gregkh is looking disappointed at you :-). I checked, and it looks like you didn't apply it to you 4.15 tree. See end for links to the fix etc.
For users: The workaround is to add "scsi_mod.scan=sync" on the kernel command line (i.e. edit /etc/default/grub and run `update-grub`). Please note 1. AFAICT this is near-universal. It affects all desktop users of kernel 4.15/4.16 who use suspend (and whose workloads use all their RAM). It could be avoided by not using SCSI, but it does affect all systems with root on SATA. 2. Although this is horrible when it happens (X crash) and can happen on a near-daily basis, it can be quite difficult for users to analyze and report. For example, the crash doesn't have one specific backtrace in Xorg. It tends to generate several different backtraces, non-deterministicly. Sometimes, making a coredump fails, presumably due to the same bug that causes the crash. I remember that Sosha had to make two attempts at reporting this bug (though I don't remember what was wrong with the first one). Also, it's triggered by a medium-term SIGALRM timer in Xorg. This made it really annoying to reproduce, at the time when I didn't know the root cause. I was able to reproduce the memory pressure needed, but it didn't happen when testing suspend+resume... only when I broke for lunch and left the machine suspended for long enough :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable /linux- stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-23.25 (ubuntu bionic): https://git.launchpad.net /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk- core.c?id=Ubuntu-4.15.0-23.25#n856 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1760450 Title: [nvidia] Xorg crashed with signal 7 in _dl_fixup() from _dl_runtime_resolve_xsavec() called from nvidia_drv.so Status in xorg-server package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: after login session(suspend mode) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 20:34:29 2018 DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg InstallationDate: Installed on 2017-09-02 (211 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: Signal: 7 SourcePackage: xorg-server StacktraceTop: _dl_fixup (l=0x559c10faa5a0, reloc_arg=<optimized out>) at ../elf/dl-runtime.c:84 _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125 ?? () from /usr/lib/xorg/modules/libwfb.so wfbComposite () from /usr/lib/xorg/modules/libwfb.so ?? () from /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so Title: Xorg crashed with signal 7 in _dl_fixup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
