☰

全新安裝時出現段錯誤和核心恐慌

tag-icon • tag-icon boot
全新安裝時出現段錯誤和核心恐慌

系統：

戴爾 XPS 9560（全新 SSD，我扔掉了舊的，因為我認為這是問題所在）

安裝：

使用所有預設 Ubuntu 19.10 選項（美式鍵盤）進行全新、獨特（非雙啟動）全磁碟加密

問題：

  1. 有時，系統會無緣無故地將自身鎖定為唯讀模式（dmesg 在 ext4 fs 上顯示無效校驗和）。下次重新啟動時，我會看到 initramfs，我點擊退出並看到 /dev/mapper/vgubuntu 已以某種方式損壞。fsck -y /dev/mapper/vgubuntu似乎解決了這個問題，但它不斷發生，我不明白為什麼
  2. 我經常在系統日誌中看到有關 lvm 身份驗證的錯誤（以及 vgs 等命令，導致 seg 錯誤）
  3. 每當我對磁碟進行更改（安裝軟體等）時，下次重新啟動都會出現上述問題之一或類似的問題，無法掛載 /sys 或 /proc 並導致核心恐慌
  4. 有時，重新啟動後，當我絕對確定我輸入的密碼正確時，加密通行證會說它不正確。從即時 USB 啟動或插入其他 USB 裝置後，往往會發生這種情況。

我有時在 dmesg 中看到的錯誤集合：

[    0.651560] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    0.651561] platform eisa.0: Cannot allocate resource for EISA slot 1
[    0.651562] platform eisa.0: Cannot allocate resource for EISA slot 2
[    0.651563] platform eisa.0: Cannot allocate resource for EISA slot 3
[    0.651563] platform eisa.0: Cannot allocate resource for EISA slot 4
[    0.651564] platform eisa.0: Cannot allocate resource for EISA slot 5


[    1.763858] psmouse serio1: synaptics: Unable to query device: -5


[    7.648072] psmouse serio1: Failed to enable mouse on isa0060/serio1


[   86.579184] ACPI BIOS Error (bug): Failure creating named object [\_GPE.XTBT.SPRT], AE_ALREADY_EXISTS (20190703/dswload2-323)
[   86.579191] No Local Variables are initialized for Method [XTBT]
[   86.579192] Initialized Arguments for Method [XTBT]:  (2 arguments defined for method invocation)
[   86.579193]   Arg0:   0000000046316a7d <Obj>           Integer 000000000000000F
[   86.579196]   Arg1:   000000000e8a068c <Obj>           Integer 0000000001060002
[   86.579198] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220)
[   86.579200] ACPI Error: Aborting method \_GPE.XTBT due to previous error (AE_ALREADY_EXISTS) (20190703/psparse-529)
[   86.579203] ACPI Error: Aborting method \_GPE.XTBT due to previous error (AE_ALREADY_EXISTS) (20190703/psparse-529)
[   86.579207] ACPI Error: Aborting method \_GPE._E42 due to previous error (AE_ALREADY_EXISTS) (20190703/psparse-529)
[   86.579209] ACPI: Marking method _E42 as Serialized because of AE_ALREADY_EXISTS error
[   86.579211] ACPI Error: AE_ALREADY_EXISTS, while evaluating GPE method [_E42] (20190703/evgpe-511)

[  127.741599] xhci_hcd 0000:3e:00.0: PCI post-resume error -19!
[  127.741601] xhci_hcd 0000:3e:00.0: HC died; cleaning up


[  132.597573] pcieport 0000:00:1d.6: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  132.597580] pcieport 0000:00:1d.6: AER:   device [8086:a11e] error status/mask=00002001/00002000
[  132.597585] pcieport 0000:00:1d.6: AER:    [ 0] RxErr     

[  311.159682] show_signal: 12 callbacks suppressed
[  311.159684] traps: cp[4842] general protection fault ip:7fd3e1a395eb sp:7fff8c268f60 error:0 in ld-2.30.so[7fd3e1a2d000+22000]
[  311.165259] traps: mv[4852] general protection fault ip:7f0685fba5eb sp:7ffd72e0f060 error:0 in ld-2.30.so[7f0685fae000+22000]
[  311.165837] traps: mv[4853] general protection fault ip:7fce112145eb sp:7ffcc6cfc6e0 error:0 in ld-2.30.so[7fce11208000+22000]
[  311.167707] traps: cp[4856] general protection fault ip:7f491a6295eb sp:7fff38c88800 error:0 in ld-2.30.so[7f491a61d000+22000]
[  311.233657] traps: mv[4866] general protection fault ip:7f379fe635eb sp:7ffd5ebbd560 error:0 in ld-2.30.so[7f379fe57000+22000]
[  311.234862] traps: mv[4867] general protection fault ip:7f89b80a35eb sp:7ffc744939a0 error:0 in ld-2.30.so[7f89b8097000+22000]
[  311.237978] traps: cp[4870] general protection fault ip:7f7de76835eb sp:7fffa43d1310 error:0 in ld-2.30.so[7f7de7677000+22000]
[  311.244466] traps: mv[4880] general protection fault ip:7f5f4da2b5eb sp:7ffcb4e1df40 error:0 in ld-2.30.so[7f5f4da1f000+22000]
[  311.244995] traps: mv[4881] general protection fault ip:7f08aa3525eb sp:7fff3ea38990 error:0 in ld-2.30.so[7f08aa346000+22000]
[  311.246672] traps: cp[4884] general protection fault ip:7fc825b9e5eb sp:7ffeaab5beb0 error:0 in ld-2.30.so[7fc825b92000+22000]
[  494.551262] show_signal: 17 callbacks suppressed
[  494.551264] traps: nautilus[5989] general protection fault ip:7f974d2cd5eb sp:7ffc7e8f6840 error:0 in ld-2.30.so[7f974d2c1000+22000]
[  494.709609] traps: nautilus[6025] general protection fault ip:7f78f919a5eb sp:7ffe197c5060 error:0 in ld-2.30.so[7f78f918e000+22000]
[  494.904602] traps: nautilus[6051] general protection fault ip:7fa5143dc5eb sp:7ffdad2aeff0 error:0 in ld-2.30.so[7fa5143d0000+22000]
[  500.109844] traps: systemd-sysctl[6266] general protection fault ip:7f4b4527a5eb sp:7ffe42750720 error:0 in ld-2.30.so[7f4b4526e000+22000]
[  500.122071] traps: sed[6279] general protection fault ip:7f43647325eb sp:7ffe60bbe830 error:0 in ld-2.30.so[7f4364726000+22000]
[  500.126567] traps: busctl[6281] general protection fault ip:7ff757e1f5eb sp:7ffd4cc4f6c0 error:0 in ld-2.30.so[7ff757e13000+22000]
[  502.161144] traps: systemd-sysctl[6352] general protection fault ip:7f44b3d845eb sp:7ffc50bd2ab0 error:0 in ld-2.30.so[7f44b3d78000+22000]
[  502.176836] traps: sed[6362] general protection fault ip:7fb4dc0ab5eb sp:7fff3294aa30 error:0 in ld-2.30.so[7fb4dc09f000+22000]
[  502.179966] traps: busctl[6364] general protection fault ip:7fb8f93395eb sp:7ffe0e5bb7f0 error:0 in ld-2.30.so[7fb8f932d000+22000]
[  504.205440] traps: systemd-sysctl[6422] general protection fault ip:7ff1f6e875eb sp:7ffee41a8cb0 error:0 in ld-2.30.so[7ff1f6e7b000+22000]
[  504.245245] traps: sed[6445] general protection fault ip:7f56bf3965eb sp:7ffd170158a0 error:0 in ld-2.30.so[7f56bf38a000+22000]
[  504.247926] traps: busctl[6448] general protection fault ip:7f76866525eb sp:7ffee3dd5880 error:0 in ld-2.30.so[7f7686646000+22000]
[  504.302730] traps: mv[6470] general protection fault ip:7f5add4545eb sp:7ffe2fdcd470 error:0 in ld-2.30.so[7f5add448000+22000]

啟動錯誤集合：

相關內容