Bug 139088 - [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error
Summary: [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-acpi (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-23 17:30 UTC by Alphazo
Modified: 2018-05-28 19:50 UTC (History)
1 user (show)

See Also:


Attachments
Custom DSDT (5.64 KB, application/x-compressed)
2014-07-20 01:42 UTC, steven_nikkel
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alphazo 2009-09-23 17:30:02 UTC
I installed 8.1 on a 1.5TB SATA drive connected to an Intel D945GCFL2. Please note that I disabled HyperThreading mode in BIOS. My system was here doing nothing (prompt). And I got some kind of disk panic that made my system reboot.
At reboot I saw that a fsck was running in the background and then I got a ACPI Exception: AE_AML_INFINITE_LOOP error coming that would fills up my terminal pretty quickly. I decided to reboot, the fsck went to the end this time and the ACPI error didn't happen.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-09-28 03:55:03 UTC
Responsible Changed
From-To: freebsd-i386->freebsd-acpi

Over to maintainer(s).
Comment 2 akripo 2010-08-15 09:25:38 UTC
Hello to all,

I have exaclty the same problem as well, which occures very often:=20

Aug 15 10:00:06 hercules kernel: ACPI Error (psparse-0633): Method =
parse/execution failed [\_SB_.PCI0.LPC_.SMBR] (Node 0xffffff00014ad3a0), =
AE_AML_INFINITE_LOOP
Aug 15 10:00:06 hercules kernel: ACPI Error (psparse-0633): Method =
parse/execution failed [\_SB_.PCI0.LPC_.INIT] (Node 0xffffff00014ad3c0), =
AE_AML_INFINITE_LOOP
Aug 15 10:00:06 hercules kernel: ACPI Error (psparse-0633): Method =
parse/execution failed [\_GPE._L00] (Node 0xffffff0001320b40), =
AE_AML_INFINITE_LOOP
Aug 15 10:00:06 hercules kernel: ACPI Exception: AE_AML_INFINITE_LOOP, =
while evaluating GPE method [_L00] (20100331/evgpe-629)
Aug 15 10:00:09 hercules kernel: ACPI Error (psparse-0633): Method =
parse/execution failed [\_SB_.PCI0.LPC_.SMBR] (Node 0xffffff00014ad3a0), =
AE_AML_INFINITE_LOOP
Aug 15 10:00:09 hercules kernel: ACPI Error (psparse-0633): Method =
parse/execution failed [\_SB_.PCI0.LPC_.INIT] (Node 0xffffff00014ad3c0), =
AE_AML_INFINITE_LOOP
Aug 15 10:00:09 hercules kernel: ACPI Error (psparse-0633): Method =
parse/execution failed [\_GPE._L00] (Node 0xffffff0001320b40), =
AE_AML_INFINITE_LOOP
.
.
.
.
.
and so on..


Motherboard: Intel D945GCFL2 with 2GB memory module
Hard disk: Segate Barracuda 7200.12 SATA 3Gb/s 1TB
FreeBSD 8.1-RELEASE amd64 with stock GENERIC kernel


BR=
Comment 3 Hiren Panchasara 2013-04-30 07:51:02 UTC
Can you try CURRENT or any fairly recent snapshot and see if this is
still an issue?

Thanks,
Hiren
Comment 4 steven_nikkel 2014-07-20 01:42:54 UTC
Created attachment 144805 [details]
Custom DSDT

https://forums.freebsd.org/viewtopic.php?p=62755#p62755

However, there is another problem with this board - broken ACPI. If you see AE_AML_INFINITE_LOOP ACPI errors on yours, load the attached DSDT.
Comment 5 steven_nikkel 2014-07-20 01:45:28 UTC
I have the exact same problem and the same board.

I believe I experienced the problem in 8.x, but don't recall what I did to resolve it. It may have been an upgrade to 9.x or a BIOS update or something else. However the problem returned in 10.x.

I found two other threads discussing the same issue:
https://forums.freebsd.org/viewtopic.php?p=62755#p62755
https://bugzilla.kernel.org/show_bug.cgi?id=14552#c6

Summary: a bug in the BIOS tables, solved by overriding them with custom DSDT tables

I've used the custom DSDT table for several months with no more occurrences of this issue.
Comment 6 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:50:27 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.