Bug 121439

Summary: [boot] Installation of FreeBSD 7.0 fails: ACPI problem with abit ip35 pro
Product: Base System Reporter: paul <paul.antonescu>
Component: amd64Assignee: freebsd-acpi (Nobody) <acpi>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description paul 2008-03-06 20:20:00 UTC 
Trying to install all of the above mentioned FreeBSD releases fails with
an ACPI error (Error: Method execution failed [\_TZ_.THRM._TMP] (Node
0xc8377700), AE_AML_NO_RETURN_VALUE ). If I try to start with ACPI disabled,
the installation freezes trying to load the install image.

How-To-Repeat: Reinstalling FreeBSD.
Comment 1 itz 2008-03-17 14:39:08 UTC 
I have the same board and a similar problem installing 7.0

I was able to install by setting SATA controller from IDE to AHCI mode with
ACPI. My workaround configuration is to set thermal polling rate to a very
high number, so the exception occurs only once during boot.

It is workable, but far from ideal:
1. I cannot boot without ACPI (system hangs apparently trying to mount /)
2. Thermal still does not work and throws exceptions. Perhaps there is a fix
to ACPI table for this?
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2009-06-20 00:09:11 UTC 
Responsible Changed
From-To: freebsd-amd64->freebsd-acpi

Over to maintainer(s).
Comment 3 dannyburkland 2009-06-20 16:50:09 UTC 
I don't have the exact same board (ASUS P5K Deluxe also p35) but had a  
similar issue. Even when I set IDE to AHCI it would still lockup if I  
tried to install from CD. However if I loaded the kernel from the cd,  
removed the disk at the loader screen, and performed a network install  
it ran great. Just recently I tried installing a 7.2 Stable snapshot  
from CD which suffered none of the issues described above. If I may  
suggest something try installing a recent 7.2 snapshot from CD and  
post back your results.

Dan

Sent from my iPhone
Comment 4 Andriy Gapon freebsd_committer freebsd_triage 2010-12-05 10:47:37 UTC 
Can you still reproduce the issue with the recent FreeBSD versions?
There is a followup suggesting that the issue could have been resolved.

-- 
Andriy Gapon
Comment 5 Andriy Gapon freebsd_committer freebsd_triage 2010-12-05 19:38:00 UTC 
State Changed
From-To: open->closed

The issue has been resolved.