SpaceInvaderOne Posted January 24, 2016 Share Posted January 24, 2016 I am sure this is down to the bios in my motherboard not being properly acpi compliant. The system works okay but i worry this may have a negative inpact on the system. I have tried all bios revisions on my mb, ASRock - Z170M Extreme4 and is same. Should i worry or just ignore? What will this error cause? Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 24 21:20:34 Prime kernel: ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8804854732d0), AE_NOT_FOUND (20150410/psparse-536) Jan 24 21:20:34 Prime kernel: ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20150410/evgpe-592) Jan 24 21:20:34 Prime kernel: ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Also when i goto tools , system log. I see following error and nothing else. Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 111 bytes) in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(280) : eval()'d code on line 73 When i run diagnostics and look at the syslog.txt it is 133 megs! it is full of the ACPI Exception: AE_NOT_FOUND error. Quote Link to comment
zoggy Posted January 25, 2016 Share Posted January 25, 2016 I've always got these myself, never been an issue. You might just check if a BIOS update is available from the manufacturer, otherwise, just ignore the errors if everything is working. Jan 19 10:30:01 husky kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150410/hwxface-580) Jan 19 10:30:01 husky kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580) Jan 19 10:30:01 husky kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Jan 19 10:30:01 husky kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88011a863898), AE_NOT_FOUND (20150410/psparse-536) Quote Link to comment
SpaceInvaderOne Posted January 25, 2016 Author Share Posted January 25, 2016 The main thing that worries me is it fills the syslog file. Making it 133 meg, then nothing else can be written to it Quote Link to comment
zoggy Posted January 30, 2016 Share Posted January 30, 2016 that is a bit odd, on mine those messages only appear once on boot of the box. Quote Link to comment
dan0luk Posted February 11, 2016 Share Posted February 11, 2016 I've got the same issue with the error messages. Intel Core i5 6500 on Asrock Z170 Pro4s. I see the messages on boot and then in the unraid web interface Logs section. My major issue is that it fills my logs memory to 100% in 2-3 min form boot-up. More worrying is that cpu core 0 is ALWAYS at 100% load. This means slower performace and higher power consumption, because 1 core is at 100% the CPU never goes in powersaving mode. Does anyone have any idea about how to solve this problem? My MB is on the latest BIOS update. Is this an unraid-Skylake issue, unraid-Z170 issue or an unraid-asrock one (are there similar issues with skylake cpus on other motherboard brands)? Quote Link to comment
dan0luk Posted February 11, 2016 Share Posted February 11, 2016 I've managed to stop the errors (and the other side-effects) by logging in terminal IMMEDIATELY after bootup and entering the command: echo "disable" > /sys/firmware/acpi/interrupts/gpe6F I'm not that up-to-date with linux config and don't at the moment know how to add the command at startup. (If anyone can help this noob, thanks in advance) Hope this helps. Quote Link to comment
SpaceInvaderOne Posted February 12, 2016 Author Share Posted February 12, 2016 I added it to my go file which wil run it as soon as unraid boots goto your flash drive then in the folder config you will see a file called go. You need to edit this file and add the line #disable gpe for bios acpi error echo disable > /sys/firmware/acpi/interrupts/gpe6F the part #disable gpe for bios api error is just to name what the line does and isnt actually necessary Quote Link to comment
RobJ Posted February 13, 2016 Share Posted February 13, 2016 Nice work hunting down 'gpe6f'! I suspect you both need to either keep monitoring for another BIOS update, or hope for a workaround in a future Linux kernel. That's how it usually works. You're apparently too close to the 'bleeding edge'. Quote Link to comment
SpaceInvaderOne Posted February 13, 2016 Author Share Posted February 13, 2016 Nice work hunting down 'gpe6f'! I suspect you both need to either keep monitoring for another BIOS update, or hope for a workaround in a future Linux kernel. That's how it usually works. You're apparently too close to the 'bleeding edge'. Yes I think its a z170 problem not just Asrock problem.Hopefully a bios update can address this although asrock just say that it is because skylake only put into linux kernal from 4.3 However the problem had been reported on https://bugzilla.kernel.org/show_bug.cgi?id=105491 and that was with kernal 4.3.0 rc4 I am happy with how my system is now with unraid, but I didnt except so many problems going to skylake. Some of the problems are here http://lime-technology.com/forum/index.php?topic=46141.msg441036#msg441036 I think maybe we should post some topics for each motherboard chipset where we can post problems we have had for various issues to help others with the same hardware or others who are thinking of buying the same. We should do the same with gpu types. Just to try and get the info in some logical order Quote Link to comment
Whaler_99 Posted March 3, 2017 Share Posted March 3, 2017 Thanks for this, was having this exact issue on a new ASRock board, core i5 6400.... adding that line into my GO file fixed it up. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.