Bug 43229
| Summary: | ACPI DSSP namespace lookup issue - Asus P8P67-EVO w/ BIOS rev 3207 | ||
|---|---|---|---|
| Product: | ACPI | Reporter: | Sami Liedes (sami.liedes) |
| Component: | BIOS | Assignee: | Lv Zheng (lv.zheng) |
| Status: | CLOSED DOCUMENTED | ||
| Severity: | normal | CC: | acpi-bugzilla, aros, bjorn, cerebellum, danyer, dsmythies, hugh, lenb, lv.zheng, martin.suc, Robert.Moore, rui.zhang, trygvis, very.evil.odmin, wrar |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.3.2, 3.3.5 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Bug Depends on: | 43225 | ||
| Bug Blocks: | |||
| Attachments: |
full dmesg output
acpidump output ACPI dump for Asus P8P67 Pro [DBG PATCH] ACPI/libata: Add libata.noacpi support bisection results and log |
||
Created attachment 73248 [details]
acpidump output
As far as the namespace lookup errors:
>>ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
There is no DSSP object defined in any of the static ACPI tables. One of the SSDTs for this machine performs some dynamic table loads, so it may be the case that DSSP is defined in one of those. However, something is still wrong because the object cannot be found.
This looks like some kind of BIOS error and should be reported to the manufacturer.
Unfortunately, the standard response from Asus to all such reports seems to be "We are not [sic] supporting Linux"... So, these dynamic table loads would probably load those tables from the BIOS? I don't know much about ACPI, but I think I could learn and try to investigate this myself... Would appreciate any useful pointers though :) hm, I have similar problem - mobo: maximus iv extreme R3 P67, BIOS:3208: May 31 11:16:28 PCEUBU1 kernel: [ 2.548912] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359) May 31 11:16:28 PCEUBU1 kernel: [ 2.548915] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff8807fac9a3c0), AE_NOT_FOUND (20110623/psparse-536) May 31 11:16:28 PCEUBU1 kernel: [ 2.548997] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359) May 31 11:16:28 PCEUBU1 kernel: [ 2.549000] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8807fac9a2d0), AE_NOT_FOUND (20110623/psparse-536) May 31 11:16:28 PCEUBU1 kernel: [ 2.549225] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359) May 31 11:16:28 PCEUBU1 kernel: [ 2.549231] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8807fac9a258), AE_NOT_FOUND (20110623/psparse-536) May 31 11:16:28 PCEUBU1 kernel: [ 2.549237] ata2.00: ATA-8: Hitachi HDS5C3020ALA632, ML6OA580, max UDMA/133 May 31 11:16:28 PCEUBU1 kernel: [ 2.549239] ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA May 31 11:16:28 PCEUBU1 kernel: [ 2.549283] ata4.00: ATA-8: Hitachi HDS721010CLA332, JP4OA3MA, max UDMA/133 May 31 11:16:28 PCEUBU1 kernel: [ 2.549285] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA May 31 11:16:28 PCEUBU1 kernel: [ 2.549416] ata1.00: configured for UDMA/133 May 31 11:16:28 PCEUBU1 kernel: [ 2.549422] async_waiting @ 5 May 31 11:16:28 PCEUBU1 kernel: [ 2.549424] async_continuing @ 5 after 0 usec May 31 11:16:28 PCEUBU1 kernel: [ 2.549481] scsi 0:0:0:0: Direct-Access ATA ST2000DL003-9VT1 CC32 PQ: 0 ANSI: 5 May 31 11:16:28 PCEUBU1 kernel: [ 2.549551] calling 12_sd_probe_async+0x0/0x1d0 @ 83 May 31 11:16:28 PCEUBU1 kernel: [ 2.549573] sd 0:0:0:0: Attached scsi generic sg0 type 0 May 31 11:16:28 PCEUBU1 kernel: [ 2.549591] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) May 31 11:16:28 PCEUBU1 kernel: [ 2.549607] initcall 2_async_port_probe+0x0/0x70 returned 0 after 313688 usecs May 31 11:16:28 PCEUBU1 kernel: [ 2.549654] sd 0:0:0:0: [sda] Write Protect is off May 31 11:16:28 PCEUBU1 kernel: [ 2.549656] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 May 31 11:16:28 PCEUBU1 kernel: [ 2.549673] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA May 31 11:16:28 PCEUBU1 kernel: [ 2.550419] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359) May 31 11:16:28 PCEUBU1 kernel: [ 2.550422] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff8807fac9a3c0), AE_NOT_FOUND (20110623/psparse-536) May 31 11:16:28 PCEUBU1 kernel: [ 2.550451] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359) May 31 11:16:28 PCEUBU1 kernel: [ 2.550453] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8807fac9a2d0), AE_NOT_FOUND (20110623/psparse-536) May 31 11:16:28 PCEUBU1 kernel: [ 2.550668] ata2.00: configured for UDMA/133 May 31 11:16:28 PCEUBU1 kernel: [ 2.550673] async_waiting @ 41 May 31 11:16:28 PCEUBU1 kernel: [ 2.550675] async_continuing @ 41 after 0 usec May 31 11:16:28 PCEUBU1 kernel: [ 2.550714] scsi 1:0:0:0: Direct-Access ATA Hitachi HDS5C302 ML6O PQ: 0 ANSI: 5 May 31 11:16:28 PCEUBU1 kernel: [ 2.550759] calling 13_sd_probe_async+0x0/0x1d0 @ 5 May 31 11:16:28 PCEUBU1 kernel: [ 2.550775] sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) May 31 11:16:28 PCEUBU1 kernel: [ 2.550785] sd 1:0:0:0: Attached scsi generic sg1 type 0 May 31 11:16:28 PCEUBU1 kernel: [ 2.550787] ata4.00: configured for UDMA/133 May 31 11:16:28 PCEUBU1 kernel: [ 2.550792] async_waiting @ 72 May 31 11:16:28 PCEUBU1 kernel: [ 2.550801] sd 1:0:0:0: [sdb] Write Protect is off May 31 11:16:28 PCEUBU1 kernel: [ 2.550803] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 May 31 11:16:28 PCEUBU1 kernel: [ 2.550813] initcall 3_async_port_probe+0x0/0x70 returned 0 after 314820 usecs May 31 11:16:28 PCEUBU1 kernel: [ 2.550815] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA May 31 11:16:28 PCEUBU1 kernel: [ 2.550827] async_continuing @ 71 after 2936 usec May 31 11:16:28 PCEUBU1 kernel: [ 2.550831] initcall 4_async_port_probe+0x0/0x70 returned 0 after 314786 usecs May 31 11:16:28 PCEUBU1 kernel: [ 2.550838] async_continuing @ 72 after 42 usec May 31 11:16:28 PCEUBU1 kernel: [ 2.550867] scsi 3:0:0:0: Direct-Access ATA Hitachi HDS72101 JP4O PQ: 0 ANSI: 5 May 31 11:16:28 PCEUBU1 kernel: [ 2.550909] calling 14_sd_probe_async+0x0/0x1d0 @ 71 May 31 11:16:28 PCEUBU1 kernel: [ 2.550930] sd 3:0:0:0: Attached scsi generic sg2 type 0 May 31 11:16:28 PCEUBU1 kernel: [ 2.550937] sd 3:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) May 31 11:16:28 PCEUBU1 kernel: [ 2.550954] initcall 5_async_port_probe+0x0/0x70 returned 0 after 314872 usecs May 31 11:16:28 PCEUBU1 kernel: [ 2.550961] sd 3:0:0:0: [sdc] Write Protect is off May 31 11:16:28 PCEUBU1 kernel: [ 2.550963] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 May 31 11:16:28 PCEUBU1 kernel: [ 2.550972] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA May 31 11:16:28 PCEUBU1 kernel: [ 2.551665] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359) May 31 11:16:28 PCEUBU1 kernel: [ 2.551668] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff8807fac9a438), AE_NOT_FOUND (20110623/psparse-536) May 31 11:16:28 PCEUBU1 kernel: [ 2.551674] ata5.00: ATAPI: PIONEER BD-RW BDR-206M, 1.04, max UDMA/100 May 31 11:16:28 PCEUBU1 kernel: [ 2.555763] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359) May 31 11:16:28 PCEUBU1 kernel: [ 2.555767] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff8807fac9a438), AE_NOT_FOUND (20110623/psparse-536) May 31 11:16:28 PCEUBU1 kernel: [ 2.555774] ata5.00: configured for UDMA/100 May 31 11:16:28 PCEUBU1 kernel: [ 2.556316] async_waiting @ 73 May 31 11:16:28 PCEUBU1 kernel: [ 2.556319] async_continuing @ 73 after 0 usec asus technical support is really useless. I reported many BIOS errors but they don't care anyway. (does not really matter if error/s corresponding with windows or linux). On P8Z77-V LE on 3.4.1: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88031084fde8), AE_NOT_FOUND (20120320/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff88031084fed8), AE_NOT_FOUND (20120320/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88031084fe60), AE_NOT_FOUND (20120320/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88031084fde8), AE_NOT_FOUND (20120320/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff88031084fed8), AE_NOT_FOUND (20120320/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88031084fe60), AE_NOT_FOUND (20120320/psparse-536) I have the same problem on a GigaByte H77M-D3H and I read somewhere else that it also happens on Intel H77/Z77 motherboards: [ 0.962043] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) [ 0.962054] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff88021508ae10), AE_NOT_FOUND (20120320/psparse-536) [ 0.962104] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) [ 0.962110] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88021508af00), AE_NOT_FOUND (20120320/psparse-536) [ 0.962158] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) [ 0.962166] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88021508ae88), AE_NOT_FOUND (20120320/psparse-536) [ 0.966398] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) [ 0.966420] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff88021508ad98), AE_NOT_FOUND (20120320/psparse-536) [ 0.966900] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) [ 0.966909] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff88021508ae10), AE_NOT_FOUND (20120320/psparse-536) [ 0.967072] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) [ 0.967081] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88021508ae88), AE_NOT_FOUND (20120320/psparse-536) [ 0.967339] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) [ 0.967345] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88021508af00), AE_NOT_FOUND (20120320/psparse-536) [ 0.968453] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) [ 0.968462] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88021508aca8), AE_NOT_FOUND (20120320/psparse-536) [ 0.976172] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) [ 0.976181] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff88021508ad98), AE_NOT_FOUND (20120320/psparse-536) [ 0.978439] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) [ 0.978447] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88021508aca8), AE_NOT_FOUND (20120320/psparse-536) I got an acpidump and disassembled the SDT tables.
The DSSP reference is within the SSDT2. It says:
External (FHPP)
[ ... ]
Device (SPT0)
{
Name (_ADR, 0xFFFF)
Method (_GTF, 0, NotSerialized)
{
Store (Zero, CMDC)
If (LOr (DSSP, FHPP))
{
GTFB (STFD, 0x06)
}
Else
{
GTFB (STFE, 0x06)
}
GTFB (FZTF, Zero)
GTFB (DCFL, Zero)
Return (SCBF)
}
}
The last part is repeated for every sata port.
Sami, I think you might be seeing two problems: (1) the ACPI DSSP namespace lookup issue, and (2) the DMA Read translation faults. Since this bug report is mostly chasing (1), can you open a new bug report for the other? Please attach the complete dmesg log and "lspci -vv" output, and cc: me (bhelgaas@google.com). If it's possible to revert to the previous BIOS version, and if that makes any difference, please attach a dmesg log on that BIOS as well. ASUS P8Z77-V PRO; BIOS 1805; kernel 3.8.0-rc5 [ 2.215990] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359) [ 2.215993] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff880214e8e5f0), AE_NOT_FOUND (20121018/psparse-537) [ 2.216069] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359) [ 2.216072] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff880214e8e668), AE_NOT_FOUND (20121018/psparse-537) [ 2.217242] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359) [ 2.217244] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff880214e8e5f0), AE_NOT_FOUND (20121018/psparse-537) [ 2.217317] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359) [ 2.217319] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff880214e8e668), AE_NOT_FOUND (20121018/psparse-537) [ 2.221242] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359) [ 2.221244] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff880214e8e578), AE_NOT_FOUND (20121018/psparse-537) [ 2.227429] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359) [ 2.227431] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff880214e8e578), AE_NOT_FOUND (20121018/psparse-537) HP Elite 7500 (Ivy Bridge Z75 chipset, i7 3770, Formosa motherboard) ; BIOS 8.17A; kernel 3.7.10 [ 0.921334] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 0.921338] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff880119a936e0), AE_NOT_FOUND (20120913/psparse-536) [ 0.921903] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 0.921907] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff880119a936e0), AE_NOT_FOUND (20120913/psparse-536) [ 0.922232] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 0.922236] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff880119a93758), AE_NOT_FOUND (20120913/psparse-536) [ 0.924677] [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 0.924679] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff880119a93758), AE_NOT_FOUND (20120913/psparse-536) [ 0.924798] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 0.924802] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff880119a938c0), AE_NOT_FOUND (20120913/psparse-536) [ 0.929516] [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 0.929518] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff880119a938c0), AE_NOT_FOUND (20120913/psparse-536) P8Z77-V; BIOS 18.05; kernel 3.7.1 [ 0.692712] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 0.692715] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f304c150), AE_NOT_FOUND (20120913/psparse-536) [ 0.711919] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 0.711921] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f304c150), AE_NOT_FOUND (20120913/psparse-536) [223256.040834] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [223256.040836] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f304c150), AE_NOT_FOUND (20120913/psparse-536) [223256.048511] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [223256.048513] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f304c150), AE_NOT_FOUND (20120913/psparse-536) Even in my case, after updating the BIOS and get this error stopped working hot plug SATA devices [ 0.962043] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) This is typically a BIOS bug. (In reply to comment #12) > [ 0.962043] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND > (20120320/psargs-359) > > > This is typically a BIOS bug. What really sucks (I'm sorry for using that word) is that this bug is present on a broad range of motherboards including Asus, Asrock and MSI, which tells me that this is not just a BIOS bug, it's a result of some change propagating from either Intel or Award (I'm inclined to think it's Intel's fault). It's an AMI bios: 0000: 44 53 44 54 6d bb 00 00 02 e2 41 4c 41 53 4b 41 DSDTm.....ALASKA 0010: 41 20 4d 20 49 00 00 00 15 00 00 00 49 4e 54 4c A M I.......INTL Created attachment 98021 [details] ACPI dump for Asus P8P67 Pro (In reply to comment #14) > It's an AMI bios: > > 0000: 44 53 44 54 6d bb 00 00 02 e2 41 4c 41 53 4b 41 DSDTm.....ALASKA > 0010: 41 20 4d 20 49 00 00 00 15 00 00 00 49 4e 54 4c A M I.......INTL You're right, it's the same here. As a vendor who stands beyond ACPI standards you could have talked to AMI and resolved this issue once and for all. Confirmed there is no DSSP, FHPP in the namespace.
They are referenced by SPTx._GTF methods.
Device (SPT0)
{
Name (_ADR, 0xFFFF) // _ADR: Address
Method (_GTF, 0, NotSerialized) // _GTF: Get Task File
{
Store (Zero, CMDC)
If (LOr (DSSP, FHPP))
{
GTFB (STFD, 0x06)
}
Else
{
GTFB (STFE, 0x06)
}
GTFB (FZTF, Zero)
GTFB (DCFL, Zero)
Return (SCBF)
}
}
This is a BIOS bug, we don't have any information to fix it.
(In reply to comment #16) > This is a BIOS bug, we don't have any information to fix it. So, what end users are supposed to do? OEMs will surely ignore our bug reports and requests saying their motherboards work just fine in Windows. Intel has people, resources and power to talk to AMI and motherboard manufactures to fix this issue. Saying this is "a BIOS bug" is not what Linux users expect to hear. well hell , that what asus told me - windows is just fine :-; please add boot option "libata.noacpi". does the error messages still exist? Created attachment 99271 [details]
[DBG PATCH] ACPI/libata: Add libata.noacpi support
You should also apply this patch to let libata.noacpi=1 working.
I've tested the patch on my Linux systems.
It can stop ATA_ACPI functionalities for me.
Please let me know if it works for your system, .
We will also try to see if such error message can be converted to [firmware bug] in the ACPICA. This is a BIOS bug, Linux can live with this by automatically disabling ATA_ACPI after several ACPI control methods execution failures. I have an issue with converting exception codes and error/warning messages like this to always point a finger at the BIOS. The fact is that we don't always know for sure whether this is a BIOS problem or not. In some cases, it is likely to be the BIOS, but in other cases we don't really know the culprit until the problem is debugged. The cases where we know for sure that we have a BIOS problem are things like (for example) when we find bad values in the FADT. As far as interpreter execution, however, there is always the chance that there is an interpreter bug, or some other problem associated more with ACPICA or the host OS rather than the BIOS itself. Bob I will first change the bug category to BIOS. Can we just change the error messages to [firmware bug] and debug each such error message for sure? In Linux, useless error messages will also be treated as OS bug by the vendors as the real problems will be hidden by noises. I do not think we can change such errors to "BIOS errors". Again, we do not know for sure. Moreover, this is slippery slope. Many, many ACPI errors can be traced back to the BIOS. Do we just make all errors "BIOS errors" and then "debug each such error message for sure"? I think not. Or convert all AML errors (AE_AML_*)? to BIOS errors? No. The fact is that the error happened within the ACPI subsystem and that is what the message is intended to convey. Fixing the blame on the BIOS is simply an attempt to guess at a root cause that the ACPICA software simply cannot do. It is wrong. I'm willing to change the message to something a bit more helpful, and we can provide a mechanism to stop the "Not found" message after it has been displayed once for a given executing control method. per comment #8, please open a new bug about the functional issue. This bug is about a broken BIOS causing Linux to spew warning messages about a broken BIOS. Ignore the messages, or get a computer from a vendor that validates for Linux. Closed as Documented -- will not fix. Another datapoint:
I have a Zotac Zbox ID 18 tiny PC. It has an Intel Celeron 1007U CPU.
BIOS information (from dmidecode):
Vendor: American Megatrends Inc.
Version: B211P011
Release Date: 03/13/2014
BIOS Revision: 4.6
I think that that is the latest released version.
dmesg shows me two errors:
[ 0.800942] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 0.801893] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
[ 0.801909] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88021684cca8), AE_NOT_FOUND (20140424/psparse-536)
[ 0.809045] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 0.831863] ata1.00: ATA-8: TOSHIBA MQ01ABD100, AX001A, max UDMA/100
[ 0.831872] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 0.833189] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359)
[ 0.833206] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88021684cca8), AE_NOT_FOUND (20140424/psparse-536)
[ 0.834078] ata1.00: configured for UDMA/100
Does anyone have a contact at AMI?
(In reply to D. Hugh Redelmeier from comment #26) > > Does anyone have a contact at AMI? Contact Zotac directly. AMI won't assist you - you are not their client. Created attachment 254757 [details] bisection results and log O.K. so the kernel bisection says the guilty commit is: commit b5c0875a16039d90f4cdf6b75ae4031daae01d56 Author: Lv Zheng <lv.zheng@intel.com> Date: Thu Aug 4 16:42:49 2016 +0800 ACPICA: Utilities: Introduce facility to allow Linux to set correct logging levels So it seems, at least for me, that this issue was always there, but just not reported before. If I correctly understand bug 43229, the root issue is actually a BIOS problem. I further tested on kernel 4.10-rc8, by reverting the above commit: doug@s15:~/temp-k-git/linux$ git log --oneline 1dc8c4f Revert "ACPICA: Utilities: Introduce facility to allow Linux to set correct logging levels" 7089db8 Linux 4.10-rc8 ... And indeed upon resume from suspend, those messages no longer appeared. Oh darn, I missed posted. I meant to post on bug 117461. (In reply to Doug Smythies from comment #29) > Oh darn, I missed posted. I meant to post on bug 117461. I mean bug 193531. |
Created attachment 73247 [details] full dmesg output After updating BIOS to revision 3207 on my Asus P8P67-EVO, the Marvell SATA controller no longer works apparently due to ACPI failures. (Fortunately, the P67 chipset SATA controller works just fine.) Some ACPI related lines that look like errors from dmesg (entire dmesg output attached). This is from 3.3.2 as I have an unrelated problem with 3.3.5; I also get similar error messages when booting 3.3.5. --------------------------------------------------------- [ 0.567349] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.567587] \_SB_.PCI0:_OSC invalid UUID ... [ 0.608854] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP07.PXSX._PRT] [ 0.608922] \_SB_.PCI0:_OSC invalid UUID [ 0.608923] _OSC request data:1 1f 1f [ 0.608926] pci0000:00: Requesting ACPI _OSC control (0x1d) [ 0.609008] \_SB_.PCI0:_OSC invalid UUID [ 0.609009] _OSC request data:1 0 1d [ 0.609011] pci0000:00: ACPI _OSC request failed (AE_ERROR), returned control mask: 0x1d ... [ 2.820832] firewire_ohci: Added fw-ohci device 0000:07:03.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x11 [ 2.820866] firewire_ohci: DMA context ARReq has stopped, error code: evt_unknown [ 2.820909] DRHD: handling fault status reg 3 [ 2.820916] DMAR:[DMA Read] Request device [07:00.0] fault addr fffff000 [ 2.820917] DMAR:[fault reason 02] Present bit in context entry is clear [ 2.820936] firewire_ohci: DMA context ARReq has stopped, error code: evt_unknown [ 2.820940] firewire_ohci: DMA context ARRsp has stopped, error code: evt_unknown [ 2.821424] DRHD: handling fault status reg 3 [ 2.821485] DMAR:[DMA Write] Request device [07:00.0] fault addr fffff000 [ 2.821486] DMAR:[fault reason 02] Present bit in context entry is clear [ 2.821620] firewire_ohci: inconsistent self IDs ... [ 3.410091] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120111/psargs-359) [ 3.410313] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff880215861708), AE_NOT_FOUND (20120111/psparse-536) ... [ 3.412547] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120111/psargs-359) [ 3.412551] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff8802158617f8), AE_NOT_FOUND (20120111/psparse-536) ... [ 3.413737] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120111/psargs-359) [ 3.413958] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff880215861690), AE_NOT_FOUND (20120111/psparse-536) [ 3.417207] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120111/psargs-359) [ 3.417433] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff8802158617f8), AE_NOT_FOUND (20120111/psparse-536) ... [ 19.757575] ACPI Warning: 0x000000000000f000-0x000000000000f01f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120111/utaddress-251) [ 19.757749] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver ... --------------------------------------------------------- See attached dmesg output and acpidump output.