ACPI Errors Kernel 3.17.2-1

vanquish · 2014-11-01 10:56:21

Hello,

due to BTRFS Errors I've upgraded my system to testing (Kernel 3.17.2-1). Now there are several ACPI Errors I don't know to handle/fix and if they are serious.

ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140724/hwxface-580)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140724/hwxface-580)

ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20140724/utaddress-258)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

This Errors don't occur with current release 3.17.1-1.

Another Error occurs since several releases ... I guess 3.13 or 3.14 (I don't know it exactly) this issue was not present:

ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88041e056b40), AE_NOT_FOUND (20140724/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88041e056b40), AE_NOT_FOUND (20140724/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88041e056bb8), AE_NOT_FOUND (20140724/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88041e056bb8), AE_NOT_FOUND (20140724/psparse-536)

I have workaround this with kernel parameter: libata.noacpi=1.

For my hardware I see more upcomming ACPI issues.

If more information is needed please let me know. I don't want to spam the whole log.
I don't know if there is a need to post this on any bugtracker. I've never done this, because I don't know if such posts are spam or not. oO

EDIT: Good point to mention my Hardware: CPU: i5-4440 Haswell, Mainboard: MSI H87-G43

Last edited by vanquish (2014-11-01 11:21:46)

graysky · 2014-11-01 11:09:14

I get the same thing on my i7-3770k CPU (Z77-based motherboard):

% dmesg -t | grep -i 'error\|warn\|exception'        
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140724/hwxface-580)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140724/hwxface-580)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8807ff440988), AE_NOT_FOUND (20140724/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8807ff440a00), AE_NOT_FOUND (20140724/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8807ff440988), AE_NOT_FOUND (20140724/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8807ff440a00), AE_NOT_FOUND (20140724/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff8807ff440af0), AE_NOT_FOUND (20140724/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff8807ff440af0), AE_NOT_FOUND (20140724/psparse-536)
ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20140724/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140724/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\_SB_.PCI0.LPCB.GPBX) (20140724/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140724/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\_SB_.PCI0.LPCB.GPBX) (20140724/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140724/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\_SB_.PCI0.LPCB.GPBX) (20140724/utaddress-258)
ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20140724/utaddress-258)

Last edited by graysky (2014-11-01 11:09:52)

WorMzy · 2014-11-01 12:24:27

I run on the mainline kernel, but I have these messages too. I haven't noticed anything out of the ordinary though.

EDIT: Graysky, you've had this problem for a while: https://bbs.archlinux.org/viewtopic.php … 3#p1294743

Chance are, I have too. I don't think the messages are anything to worry about.

Last edited by WorMzy (2014-11-01 12:44:47)

vanquish · 2014-11-01 14:22:44

WorMzy wrote:

I don't think the messages are anything to worry about.

That is my problem. I'm not a kernel hacker or sth. like that. But If I get things shown up like the libata/sata error message I'll get alerted. As I don't know if it's a danger for my data. To be safe I've added libata.noacpi=1 to my kernel line.
Another reason is: The Errors/Warnings/Exception are increased. Most people tend to say on acpi issues it is mainboard/bios related (manufacturers fault). But the 1st and 2nd issue shown up after upgrading 3.17.1-1 to 3.17.2-1.

So for me it's better to ask here. Before I'll open a new thread at bugtracker. Maybe there is a solution or its nothing.

graysky · 2014-11-01 14:58:21

@WorMzy - yes, it is an old problem... your sig reports that you run same motherboard as I do... can you post the output of:

dmesg -t | grep -i 'error\|warn\|exception'

Last edited by graysky (2014-11-01 14:58:31)

WorMzy · 2014-11-01 19:13:14

ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140926/hwxface-580)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140926/hwxface-580)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88040e0396e0), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88040e0396e0), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88040e039500), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88040e039500), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff88040e0395f0), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff88040e039668), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88040e039758), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88040e039578), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff88040e0395f0), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff88040e039668), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88040e039758), AE_NOT_FOUND (20140926/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140926/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88040e039578), AE_NOT_FOUND (20140926/psparse-536)
md127: Warning: Device sda1 is misaligned
ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20140926/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140926/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\_SB_.PCI0.LPCB.GPBX) (20140926/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140926/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\_SB_.PCI0.LPCB.GPBX) (20140926/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140926/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\_SB_.PCI0.LPCB.GPBX) (20140926/utaddress-258)
ACPI Warning: SystemIO range 0x000000000000f000-0x000000000000f01f conflicts with OpRegion 0x000000000000f000-0x000000000000f00f (\_SB_.PCI0.SBUS.SMBI) (20140926/utaddress-258)

graysky · 2014-11-01 19:20:02

Looks pretty consistent... plus your /dev/sda1 is misaligned

WorMzy · 2014-11-01 22:23:16

I noticed that.

One of my RAID's disk has a different sector size to the others, which is annoying, but I'll not lose any sleep over it.

vanquish wrote:

WorMzy wrote:
I don't think the messages are anything to worry about.
That is my problem. I'm not a kernel hacker or sth. like that. But If I get things shown up like the libata/sata error message I'll get alerted. As I don't know if it's a danger for my data.

I'm not a kernel hacker either, and I understand your concern. But as far as I can tell, the errors are benign. They are indicative of a faulty BIOS, or at least a BIOS that doesn't adhere to the ACPI spec. Your PC may run a little hotter than it should, or it may use a little more power, but other than that, I don't think you'll see any negative consequences. And if you do, the only things you can do are: 1) update your BIOS, and hope that fixes it, 2) Contact your motherboard manufacturer and ask them to fix it, then go back to step 1. or 3) Change your motherboard for one that adheres to the ACPI spec.

vanquish · 2014-11-02 08:47:45

Thank you for your reply. In the meanwhile I've done some research by myself.

The most "serious" impact to me is the S1/S2 issue as the shutdown does not work anymore.
Neither on KDE nor on Console via "shutdown -h now".

For the SMB thing a have not found any hints for the reason why this happen.

The SATA issue is probably hardware related (drive itself, cable or sth., drive/board incompatibility). SATA 0-3 working without any kernel message.
If I unplug one of the affected drives the associated messeage disapears.

Last edited by vanquish (2014-11-02 08:57:37)

Arch Linux

#1 2014-11-01 10:56:21

ACPI Errors Kernel 3.17.2-1

#2 2014-11-01 11:09:14

Re: ACPI Errors Kernel 3.17.2-1

#3 2014-11-01 12:24:27

Re: ACPI Errors Kernel 3.17.2-1

#4 2014-11-01 14:22:44

Re: ACPI Errors Kernel 3.17.2-1

#5 2014-11-01 14:58:21

Re: ACPI Errors Kernel 3.17.2-1

#6 2014-11-01 19:13:14

Re: ACPI Errors Kernel 3.17.2-1

#7 2014-11-01 19:20:02

Re: ACPI Errors Kernel 3.17.2-1

#8 2014-11-01 22:23:16

Re: ACPI Errors Kernel 3.17.2-1

#9 2014-11-02 08:47:45

Re: ACPI Errors Kernel 3.17.2-1

Board footer