Ubuntu 22.04在HP ProBook 450启动卡顿无响应的排查与修复求助
Ubuntu 22.04在HP ProBook 450启动卡顿无响应的排查与修复求助
我用的是HP ProBook 450,装了Ubuntu 22.04,最近启动时频繁出问题——刚显示完fsck的输出,系统就直接卡住了,屏幕上只有个不闪烁的光标,完全没响应,只能硬重启才行。每次卡顿时弹出的错误信息还不一样,但查看系统日志后发现,其实系统后台还在运行,只是控制台没反应。
我整理了卡顿时看到的一些日志信息:
执行journalctl --since today看到的部分错误:
- TPM固件bug:
kernel: tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
- 无线网卡BIOS信息异常:
kernel: iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
- 蓝牙事件格式错误:
kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
- Nvidia驱动注册失败及内核空指针错误:
[drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate NvKmsKapiDevice [drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to register device BUG: kernel NULL pointer dereference, address: 0000000000000040 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page
- GPU检测服务启动失败:
Failed to start Detect the available GPUs and deal with any system changes.
- 散热管理服务异常:
thermald[1964]: Unsupported condition 9 (Aggregate_power_percentage) thermald[1964]: Unsupported condition 9 (Aggregate_power_percentage) thermald[1964]: Unsupported conditions are present thermald[1964]: Polling mode is enabled: 4
- ACPI BIOS解析错误:
kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20220331/psargs-330) kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
- GDM环境对象引用错误:
gdm-launch-environment][3113]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
我觉得上面大部分问题应该不至于导致系统卡住,而且日志里也显示后台还在正常跑。现在我越来越怀疑是窗口系统启动失败,因为看到了这些Xorg相关的致命错误:
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) open /dev/fb0: No such file or directory Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: vesa: Ignoring device with a bound kernel driver Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Screen 0 deleted because of no matching config section. Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadModule: "modesetting" Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Screen 0 deleted because of no matching config section. Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadModule: "fbdev" Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadSubModule: "fbdevhw" Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadSubModule: "fbdevhw" Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadSubModule: "fbdevhw" Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Screen 0 deleted because of no matching config section. Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadModule: "vesa" Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Device(s) detected, but none match those in the config file. Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: Fatal server error: Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) no screens found(EE) Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: Please consult the The X.Org Foundation support Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: at http://wiki.x.org Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: for help. Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE)
现在每次开机都要试4、5次才能成功启动,有时候还得进recovery模式用boot-repair工具才行。有没有大佬能给点排查和修复的建议?对了,不管用Nvidia闭源驱动还是nouveau开源驱动,这个问题都会出现。
备注:内容来源于stack exchange,提问作者crafter
相关产品推荐
相关产品推荐

