systemd-journald 在 pthread_sigmask() 中因 SIGABRT 崩溃

Question

18.04在新的 Lenovo x1c6 上全新安装 Ubuntu ，从挂起状态恢复后有时会收到此错误。

我不知道这是什么意思，在线搜索导致不存在的错误报告

可能是相关的：我的电池寿命是 4-5 小时，而其他 Ubuntu 用户报告这个联想有 10+ 小时。查看相关线程

该线程中的答案建议运行以下命令：

?  ~ journalctl
-- Logs begin at Fri 2018-05-18 13:10:19 CEST, end at Tue 2018-05-22 19:25:25 CEST. --
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubu
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2da2702a-fc2a
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: KERNEL supported cpus:
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel:   Intel GenuineIntel
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel:   AMD AuthenticAMD
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel:   Centaur CentaurHauls
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compact
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: e820: BIOS-provided physical RAM map:
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009cfff] usable
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x000000000009d000-0x00000000000fffff] reserved
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000044f7dfff] usable
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x0000000044f7e000-0x0000000044f7efff] ACPI NVS
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x0000000044f7f000-0x0000000044f7ffff] reserved
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x0000000044f80000-0x000000004e8d9fff] usable
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x000000004e8da000-0x000000004ff1afff] reserved
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x000000004ff1b000-0x000000004ff99fff] ACPI NVS
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x000000004ff9a000-0x000000004fffefff] ACPI data
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x000000004ffff000-0x000000004fffffff] usable
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x0000000050000000-0x0000000057ffffff] reserved
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x0000000058600000-0x000000005c7fffff] reserved
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x00000000fe010000-0x00000000fe010fff] reserved
May 18 13:10:19 goldy-ThinkPad-X1-Carbon-6th kernel: BIOS-e820: [mem 0x0000000100000000-0x00000004a27fffff] usable

他的问题是通过这样做解决了他的高 CPU 问题引起的：

我通过向属性添加pci=nomsi参数来 修复它GRUB_CMDLINE_LINUX_DEFAULT（您可以在 : 中找到并编辑它 sudo vim /etc/default/grub）

添加参数后更新 grub:sudo update-grub然后重启。然后在终端中运行 top ，看看是否修复了它。

我不想在grub没有进一步建议的情况下惹来麻烦。这些天有太多变砖的计算机在运行:)

在此先感谢您的帮助！

Answer 1

我的记忆力很弱，在 systemd 区域中，某些安装可能出现了类似日志中表达的问题。解决方案是将 systemd 更新到更新的版本，其中包含解决该问题的修复程序。

Answer 2

对于与电源管理有关的奇怪且难以追踪的问题，包括挂起/恢复和休眠/唤醒，我建议的第一个步骤始终是这样的：检查您的系统固件是否是最新的，如果不是，请更新它。

根据我的经验，这解决了很多此类问题。