Bug 204567

Summary:	ACPI BIOS Error (bug)
Product:	ACPI	Reporter:	sidro (slacky2005)
Component:	BIOS	Assignee:	Zhang Rui (rui.zhang)
Status:	CLOSED INSUFFICIENT_DATA
Severity:	normal	CC:	rui.zhang
Priority:	P1
Hardware:	Intel
OS:	Linux
Kernel Version:	linux 5.2.5	Subsystem:
Regression:	No	Bisected commit-id:

Description sidro 2019-08-13 12:36:22 UTC

<3>[    3.176224] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
<3>[    3.179828] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
<6>[    3.183334] ata4.00: ATAPI: DRW-24D5MT, 1.00, max UDMA/133
<3>[    3.183507] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
<3>[    3.187061] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
<3>[    3.190699] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
<3>[    3.194265] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
<6>[    3.198023] ata2.00: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133
<6>[    3.198028] ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
<3>[    3.199336] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
<3>[    3.202939] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
<6>[    3.206452] ata4.00: configured for UDMA/133
<6>[    3.206465] ata1.00: ATA-9: BIWIN SSD, R0123A0, max UDMA/133
<6>[    3.206470] ata1.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 32), AA
<3>[    3.206645] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
<3>[    3.210223] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
<6>[    3.213953] ata2.00: configured for UDMA/133
<3>[    3.215703] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
<3>[    3.219250] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
<6>[    3.227075] ata1.00: configured for UDMA/133

Comment 1 Zhang Rui 2019-09-03 12:56:29 UTC

what's your laptop model?

I've seen exactly the same error on my toshiba z830
[   33.235369] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._SDD.GTF0], AE_NOT_FOUND (20190703/psargs-330)
[   33.237202] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._SDD due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
[   33.239231] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.GTF0], AE_NOT_FOUND (20190703/psargs-330)
[   33.241104] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)

But this is a BIOS error that we can not fix in Linux kernel.

Comment 2 Zhang Rui 2019-09-03 12:56:58 UTC

BTW, it is harmless, so don't worry about it.

Comment 3 sidro 2019-09-03 14:45:54 UTC

(In reply to Zhang Rui from comment #1)
> what's your laptop model?
> 
> I've seen exactly the same error on my toshiba z830
> [   33.235369] ACPI BIOS Error (bug): Could not resolve symbol
> [\_SB.PCI0.SAT0.PRT0._SDD.GTF0], AE_NOT_FOUND (20190703/psargs-330)
> [   33.237202] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._SDD due to
> previous error (AE_NOT_FOUND) (20190703/psparse-531)
> [   33.239231] ACPI BIOS Error (bug): Could not resolve symbol
> [\_SB.PCI0.SAT0.PRT0._GTF.GTF0], AE_NOT_FOUND (20190703/psargs-330)
> [   33.241104] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to
> previous error (AE_NOT_FOUND) (20190703/psparse-531)
> 
> But this is a BIOS error that we can not fix in Linux kernel.

It is not a laptop, it's a motherboard, GIGABYTE Z370P-D3.

Comment 4 Zhang Rui 2019-09-09 03:17:42 UTC

Please attach the acpidump output and let me confirm if this is the same BIOS issue.
If yes, I'd suggest you to try the latest BIOS upgrade and see if the problem is gone or not, but anyway, we can not fix it in the kernel.

Comment 5 Zhang Rui 2019-12-30 09:49:14 UTC

Bug closed as there is no response from the bug reporter.
Please feel free to reopen it if you can provide the information required in comment #4