ACPI BIOS 错误 (BUG):无法解析符号 [\_SB.PCIO.SATO.PRTO._GTF.DSSP] AE_NOT_FOUND (20190816/psargs-330)

Sun*_*ear 11 boot 18.04

我的 Ubuntu 18.04 系统运行良好有一段时间(几年)。它突然抛出了这个错误。导致系统多次自动重启。有时它能够启动登录,但即使在登录后,它的行为也很古怪。是什么赋予了?

linux 内核 5.4.0-42-generic

错误

更新:

  1. BIOS 已更新,解决了疯狂的自动重启问题并使系统可用。

  2. 我发现这个错误出现在18.04和16.04的dmesg日志中。下面是 ACPI 错误消息的更详细列表(我发现已发出一些相关的 ACPI 消息,但没有 ACPI 语法)。问题似乎与 _GTF 方法有关。那是什么,它有什么作用?另外,什么是 DSSP?

来自 dmesg 的有关错误的更多详细信息:

[    1.201570] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.201575] No Local Variables are initialized for Method [_GTF]
[    1.201576] No Arguments are initialized for method [_GTF]
[    1.201577] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.205307] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205311] No Local Variables are initialized for Method [_GTF]
[    1.205312] No Arguments are initialized for method [_GTF]
[    1.205313] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.249944] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.249949] No Local Variables are initialized for Method [_GTF]
[    1.249950] No Arguments are initialized for method [_GTF]
[    1.249951] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.333524] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.333529] No Local Variables are initialized for Method [_GTF]
[    1.333530] No Arguments are initialized for method [_GTF]
[    1.333531] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
Run Code Online (Sandbox Code Playgroud)

cia*_*pix 11

我在这里找到了这个问题的详细解释:长话短说(代码突出显示我自己的):

正确的修复方法就是简单地启动内核并libata.noacpi=1 再次恢复工作,YAY \o/

要使其在 Debian 上永久存在,请编辑/etc/default/grub并设置以下行:

GRUB_CMDLINE_LINUX_DEFAULT="libata.noacpi=1"
Run Code Online (Sandbox Code Playgroud)

然后通过运行重新生成 grub 配置update-grub