systemd-journald在pthread_sigmask（）中与SIGABRT崩溃

在新的lenovo x1c6上全新安装ubuntu 18.04 ，我有时会在从暂停状态恢复后出现此错误。

我不知道这意味着什么，在线搜索会导致错误报告不存在

可能是相关的：我的电池寿命是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问题造成的：

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

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

没有进一步的建议，我不想搞砸grub 。 这些天运行的砖计算机太多了:)

在此先感谢您的帮助！