ACPI? problem with release 8.0
malcolm.kay at internode.on.net
Mon Apr 12 06:01:38 UTC 2010
I desperately need to make some progress on this issue.
Is it likely that the issue is real rather than hardware
or disk corruption? Earlier releases are operating OK on the same
I have now confirmed that:
debug.acpi.disabled=acad button cpu lid thermal timer video
still leaves the system crashing and powering down when idle for
a while. And the more extensive:
debug.acpi.disabled=acad bus children button cmbat cpu ec isa
lid pci pci_link sysresource thermal timer video
does the same.
I don't really need power management but with acpi disabled the
disks are not visible to the system.
Are there sysctl variables that can influence this behaviour?
Currently I believe we have:
hw.acpi.supported_sleep_state: S1 S4 S5
machdep.idle_available: spin, amdc1e, hlt, acpi,
However on the earlier RELEASEs that work I note we do not have
machdep.idle or machdep.idle_available. Instead I find:
Although I've not been able to relate this directly to my problem
from Googling it seems that there some issues with amdc1e under
BSD, Linux and perhaps Windows. But all the references seem to
amd c1e are related to systems in 64 bit mode while I am running
(or trying to run) i386 so I wonder why I have:
Maybe my problem is not acpi as such but this idle mode.
My thought is to change this to
Any comments or ideas please!
Thank you for your attention.
On Sat, 10 Apr 2010 05:22 pm, Malcolm Kay wrote:
> My machine had two SATA 300GB drives
> (WDC WD3200KS-00PFB0 21.00M21) one carrying FreeBSD
> RELEASE-6.3 and the other RELEASE-7.0 all of which worked OK.
> Recently added SATA 1TB (WDC WD10EADS-00P8B0 01.00A01) and
> installed RELEASE 8.0 thereon. When I boot to RELEASE 8.0
> I find after some time, few minutes to rather more minutes
> the system just powers down without warning or any obvious
> cause. It seems to mostly happen when the system is relatively
> Suspecting the ACPI I added:
> to loader.conf.
> I then found RELEASE 8.0 would not boot -- or at least
> it was unable to mount root. I get a "mountroot>" prompt
> but this seemed not to accept anything I could think of,
> and "?" to list available targets yielded nothing. Rebooting
> and overriding this with option 2 (enable ACPI) in the boot
> menu took me back to a bootable but fragile system.
> Changing the loader.conf entry to:
> had the same effect as the hint.acpi.0.disabled=1.
> I then thought to be somewhat selective with
> debug.acpi.disabled and intended to try:
> debug.acpi.disabled=acad button cpu lid thermal timer video
> only now as I write this I discover I actually entered:
> debug.acpi.disabled=acadbutton cpu lid thermal timer video
> Now the RELEASE-8.0 booted but remained fragile.
> I've repaired this last entry and will proceed to try it.
> Meanwhile I feel I am fumbling about in the dark without
> sufficient (or any real) knowledge of the range of tasks
> performed by ACPI.
> Is my guess that I have an interaction problem between ACPI
> and RELEASE-8.0 a reasonable one? Where can I go from here?
> The system uses a Gigabyte GA-M55SLI-S4 mother board and the
> prcessor is AMD Athlon(tm) 64 X2 Dual Core Processor 5600+
> Please offer suggestions or comments.
> Malcolm Kay
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions