[Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
I mean, use the link "Report a bug" at the top-right of this page. Not add comments to this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
That's not enough information. At this point you should report a new bug, please. Notice the linked bug #1760450 includes a crash trace. (Not saying for sure you'd be able to do the same). The fatal signal is SIGBUS, as opposed to the usual SIGSEGV or abort. If you've got a SIGSEGV or an abort instead, you don't have this bug. If you do, you can link to this bug for the historical reminder. (The analysis of these crash traces is a bit unusual). I'd be pretty surprised if there was a regression on this. Axboe demanded a regression test for blktests, so it can't be exactly the same. And the cause of the bug was something pretty silly during the transition to blk-mq... I don't know why it would get introduced elsewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760450] Re: [nvidia] Xorg crashed with signal 7 in _dl_fixup() from _dl_runtime_resolve_xsavec() called from nvidia_drv.so
Hi Vedant. Change the line in /etc/default/grub e.g. GRUB_CMDLINE_LINUX_DEFAULT="quiet" to GRUB_CMDLINE_LINUX_DEFAULT="quiet scsi_mod.scan=sync" and then re-run update-grub. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 874936] Re: Firefox menu bar under Unity(2D) is too slow for my fingers (on Core2!)
Please do auto-close. I don't have a Unity install to test this on, 2D or otherwise. I don't plan on using community-supported Unity, partly because I think there were other reported bugs that I didn't hear anything about. Also, it looks as if the root issue is fixed for new Firefox profiles. *If* I create a new profile, then the default folder when creating a bookmark is "Other Bookmarks" (heh). So you don't end up with thousands of items in the Bookmarks menu. Unless you deliberately asked for every one of them. I wouldn't say the occurrence was a one-off, seems clear from comments that it was consistent. :-P. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874936 Title: Firefox menu bar under Unity(2D) is too slow for my fingers (on Core2!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/874936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769819] Re: [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → nvidia_drv.so+60a46c → [heap]+d35cb0
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769819 Title: [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → nvidia_drv.so+60a46c → [heap]+d35cb0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1769819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769819] Re: [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → nvidia_drv.so+60a46c → [heap]+d35cb0
CurrentDmesg.txt: [58189.152330] PM: suspend exit [58189.162027] Read-error on swap-device (253:0:361608) [58189.167038] Read-error on swap-device (253:0:361672) "People die when they are killed". Specifically "Read-error on swap- device" kills you with SIGBUS. Mystery solved. I really expect if you looked at the crash, you would notice it is SIGBUS, with si_code == BUS_ADRERR (2). This means a read error when trying to load a page of virtual memory back in from swap or from the filesystem. There's a common bug which matches this, so please read #1776887 "Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend". I'm sure this applies to at least some users who marked themselves as affected, or some duplicates of this bug. This particular kernel log includes some other errors as well though, so I can't rule out that they also have some relation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769819 Title: [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → nvidia_drv.so+60a46c → [heap]+d35cb0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1769819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Also, I can confirm Maxim Loparev's comment #12. The current -hwe kernels in Ubuntu 16.04 "Xenial" are also missing this critical kernel fix. Please can you either update the list of affected Ubuntu versions, or let us know if the bug needs reporting separately? Link to HEAD source: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/xenial/tree/block/blk-core.c?h=hwe#n856 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
I don't see it! The changelog doesn't include this fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887 the fix never reached the GIT tree to start with, unless it was force- pushed away when I wasn't looking? The interruptible wait remains present in blk-core.c. https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk- core.c?id=Ubuntu-4.15.0-29.31#n856 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Is there an estimate for when users will receive the SRU? (Which was submitted on 2018-06-29). So far I've seen 8 separate questions on askubuntu.com which match this bug. Poke :-). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775593] Re: X server crashes with SIGBUS when resuming from suspend
*** This bug is a duplicate of bug 1753012 *** https://bugs.launchpad.net/bugs/1753012 Actually for frequent suspend -> SIGBUS in Xorg on Ubuntu 18.04, you also need to look at this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775593 Title: X server crashes with SIGBUS when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1775593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760450] Re: [nvidia] Xorg crashed with signal 7 in _dl_fixup() from _dl_runtime_resolve_xsavec() called from nvidia_drv.so
Thanks for your confirmation, Julien. I have asked Ubuntu to import the proper fix from upstream and they responded very promptly. See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887 They have posted a test kernel. I don't have a ubuntu install to test it on - only a VM which cannot suspend. It *might* be useful if someone wants to volunteer to try using the test kernel. You could test that your normal suspend still works, and test the command mentioned in the commit. I.e. $ sudo -i # dd if=/dev/sda of=/dev/null iflag=direct & \ while killall -SIGUSR1 dd; do sleep 0.1; done & \ echo mem > /sys/power/state ; \ sleep 5; killall dd # stop after 5 seconds On a "bad" kernel, any time you run this command it should show a message about an IO error. On a "good" kernel, the system will appear to suspend and resume, but there should be no IO error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Awesome. Thanks. I can't test suspend in a VM, and I don't have a physical Ubuntu install. The block developers arranged a more convenient test for the underlying issue in https://github.com/osandov/blktests/ Before (i.e. linux-image-4.15.0-23-generic): $ sudo ./check block/016 block/016 (send a signal to a process waiting on a frozen queue) block/016 (send a signal to a process waiting on a frozen queue) [failed] runtime ... 8.112s --- tests/block/016.out 2018-06-15 10:05:09.080764871 +0100 +++ results/nodev/block/016.out.bad 2018-06-15 10:05:27.236769759 +0100 @@ -1,2 +1,3 @@ Running block/016 +dd: error reading '/dev/nullb0': Input/output error Test complete After (i.e. 4.15.0-23.26~lp1776887): $ sudo ./check block/016 block/016 (send a signal to a process waiting on a frozen queue) [passed] runtime 8.112s ... 10.086s $ I don't see any problem with the patched VM, though obviously it would be nice to have someone test both normal suspend and the pm_test reproducer on a physical install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Sorry, it's not convenient for me to test Ubuntu at the moment. I abuse the above instructions to assert that this bug is confirmed, citing the URLs provided. (1: The patch+description linked for kernel 4.17, 2: the lack of fix evidenced in the link for kernel 4.15.0-24.26). I appeal to authority based on me being the author of the fix, which was merged to the Linux kernel :). Furthermore, I do so on behalf of two Ubuntu users active on Ubuntu bug linked above.[1] In the first instance, I analysed the crash dump and explained the very distinct signature which it shows, indicating this bug. The second user confirmed that they suffered this bug and used a very specific workaround to avoid it. [1] https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/ (The Ubuntu bug is marked as affecting 7 people overall. I am certain this is an understatement. I mentioned in my comment in the bug, how the nature of the crashes made them hard for users to identify. One part is the same as the experience we had in Fedora. Automatically reported crashes were not reliably detected as duplicates, because the fatal SIGBUS signal can happen at a number of different points). ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776887] [NEW] Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Public bug reported: This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). 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-24.26 (ubuntu 18.04): https://git.launchpad.net /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk- core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1776887/+attachment/5152515/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
** Patch added: "A copy of the original patch that was merged upstream" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+attachment/5152516/+files/0001-block-do-not-use-interruptible-wait-anywhere.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760450] Re: [nvidia] Xorg crashed with signal 7 in _dl_fixup() from _dl_runtime_resolve_xsavec() called from nvidia_drv.so
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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760450] Re: Xorg crashed with signal 7 in _dl_fixup()
** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=1553979 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760450 Title: Xorg crashed with signal 7 in _dl_fixup() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771196] Re: daap plugin opens port by default
Thank you for fixing my silly mistake, Steve. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771196 Title: daap plugin opens port by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1771196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771196] [NEW] daap plugin opens port by default
*** This bug is a security vulnerability *** Public security bug reported: In a default installation, the daap plugin is enabled, and listens to port 3689 (daap). tcp0 0 *:daap *:* LISTEN guest-43a0me 72019 - Ubuntu has a "no open ports by default" policy.[1][2] [1] https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/753986 [2] https://wiki.ubuntu.com/SecurityTeam/Policies#No_Open_Ports Please resolve this e.g. by updating rhythmbox not to listen on a port by default, or documenting rhythmbox as an exception to the security policy. --- Ubuntu 16.04.4 LTS rhythmbox 3.3-1ubuntu7 ** Affects: banshee (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771196 Title: daap plugin opens port by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1771196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756984] Re: Xorg crashed with signal 7 in dl_new_hash()
I strongly suspect this is the same bug in upstream kernel v4.15, which causes this issue: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1760450/comments/6 I am basing this on the "signal 7" (SIGBUS), as this is relatively rare on x86 [1]. Also that it occurs inside xorg_backtrace() - this is also *supposed* to be relatively rare, because libunwind tries to use a clever trick to avoid reading wild pointers and dying with a segmentation fault [2]. [1] https://stackoverflow.com/questions/2089167/debugging-sigbus-on-x86-linux [2] https://lwn.net/Articles/502864/ I would also predict that the original fault was caused by fetching the first instruction of the function, but it looks like we don't have the symbol information for it. (boo, nvidia). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756984 Title: Xorg crashed with signal 7 in dl_new_hash() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1756984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760450] Re: Xorg crashed with signal 7 in _dl_fixup()
Hi Ubuntu users! Signal 7 is SIGBUS. SIGBUS should be relatively unusual on x86 [1]. [1] https://stackoverflow.com/questions/2089167/debugging-sigbus- on-x86-linux I'm excited to inform you that Fedora Linux users also started seeing the same root problem. It is tied to the upgrade from kernel v4.14 to v4.15. Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1553979 Arch Linux independently identified this as caused by the kernel upgrade: https://bbs.archlinux.org/viewtopic.php?id=235027 It can happen after resume from suspend, not every time but maybe once every three days. We have reports for both Xwayland and Xorg getting a fatal SIGBUS in _dl_fixup(). (While this is actually a secondary crash in xorg_backtrace(), we have a load of SIGBUS traces that have the same primary trace as each other). Notice the specific faulting instruction in disassembly you captured: it is not performing a memory access! => 0x559c102a4060 : sub$0xd8,%rsp Instead, notice that this is the first instruction in the function ErrorFSigSafe. This is a big common factor in our traces. (We actually have several different traces captured, with the failing function varying, often along the same call chain). What's happening is a fault on the instruction fetch. You should be able to confirm this if you look at the address which generates the fault. (si_addr field of struct siginfo. I don't know where the Ubuntu crash collector saves this information) The kernel failed to load in the page which holds the program code at this point. That's the real problem: some sort of transient IO error during wakeup. Users sometimes see other symptoms of these IO errors as well: PM: resume devices took 1.017 seconds Restarting tasks ... Read-error on swap-device (253:1:836184) PM: suspend exit systemd-coredump[755]: Process 1356 (Xwayland) of user 42 dumped core. and PM: suspend exit EXT4-fs error (device dm-2): ext4_find_entry:1436: inode #5514052: comm thunderbird: reading directory lblock 0 Buffer I/O error on dev dm-2, logical block 0, lost sync page write WARNING: CPU: 1 PID: 748 at fs/buffer.c:1108 mark_buffer_dirty+0xd4/0xe0 (and a kernel backtrace) ** Bug watch added: Red Hat Bugzilla #1553979 https://bugzilla.redhat.com/show_bug.cgi?id=1553979 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760450 Title: Xorg crashed with signal 7 in _dl_fixup() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
