升级到 Ubuntu 20.04.1 后 xorg 段错误 - 如何处理?

升级到 Ubuntu 20.04.1 后 xorg 段错误 - 如何处理?

我刚刚升级到 Ubuntu 20.04.1,重新启动后,屏幕变黑,光标闪烁(但无法打字)。

Xorg.0.log

[    10.307] (II) Loading sub module "fb"
[    10.307] (II) LoadModule: "fb"
[    10.310] (II) Loading /usr/lib/xorg/modules/libfb.so
[    10.311] (II) Module fb: vendor="X.Org Foundation"
[    10.311]    compiled for 1.20.8, module version = 1.0.0
[    10.311]    ABI class: X.Org ANSI C Emulation, version 0.4
[    10.311] (II) UnloadModule: "fbdev"
[    10.311] (II) Unloading fbdev
[    10.311] (II) UnloadSubModule: "fbdevhw"
[    10.311] (II) Unloading fbdevhw
[    10.311] (II) UnloadModule: "vesa"
[    10.311] (II) Unloading vesa
[    10.311] (EE) 
[    10.311] (EE) Backtrace:
[    10.312] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5580989b311c]
[    10.312] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fdec4e5841f]
[    10.313] (EE) 2: ? (?+0x0) [0x0]
[    10.313] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    10.313] (EE) 3: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fdec46fb850]
[    10.313] (EE) 4: ? (?+0x0) [0x55809a1b9f90]
[    10.313] (EE) 
[    10.313] (EE) Segmentation fault at address 0x0
[    10.313] (EE) 
Fatal server error:
[    10.313] (EE) Caught signal 11 (Segmentation fault). Server aborting

以下是文件开头的一些版本信息:

[    10.224] Build Operating System: Linux 4.15.0-115-generic x86_64 Ubuntu
[    10.224] Current Operating System: Linux abc-ThinkPad-E485 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64
[    10.224] Kernel command line: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ivrs_ioapic[32]=00:14.0 ivrs_ioapic[33]=00:00.1 iommu=pt processor.max_cstate=5 vt.handoff=7
[    10.224] Build Date: 04 September 2020  01:34:27PM
[    10.224] xorg-server 2:1.20.8-2ubuntu2.4 (For technical support please see http://www.ubuntu.com/support) 
[    10.225] Current version of pixman: 0.38.4

有什么想法可以修复它/获取更多信息吗?我不介意简单地降级 ubuntu,但我读到降级也不一定是个好主意。

我发现这个错误,这看起来有些相关。但我不知道如何恢复 mesa,也不知道这是否真的是原因。

答案1

好吧,显然我在这里问完之后就找到了解决方案。

很久以前,我安装了专有的 amdgpu 驱动程序,卸载它们解决了这个问题。如果其他人也遇到同样的问题:

/usr/bin/amdgpu-pro-uninstall

我可能会在某个时候尝试安装较新版本的驱动程序。

相关内容