☰

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

tag-icon • tag-icon 18.04 suspend lenovo systemd systemd-journald
systemd-journald 在 pthread_sigmask() 中因 SIGABRT 而崩溃

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在没有进一步建议的情况下乱搞。现在到处都是坏掉的电脑:)

提前感谢你的帮助！

答案1

我记得在 systemd 区域，一些安装存在问题，这些问题可能在类似的日志中表达出来。解决方案就是将 systemd 更新到包含可解决问题的修复程序的较新版本。

答案2

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

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

相关内容