Re: Cannot suspend system.
Garrett Cooper
> Hi I have never been able to get suspend working on my system. I've heard
> it's an acpi issue but don't know how to fix it. Can anyone help me to get
> it working?
Have you looked at
http://www.freebsd.org/doc/en/books/handbook/acpi-debug.html yet?
-Garrett
Tim Matthews
Garrett Cooper
What happens exactly when you attempt to suspend the machine? What
architecture is it? Are you running SMP? sysctl -a | grep cx_supported
says?
Thanks,
-Garrett
Tim Matthews
It doesn't suspend if I use acpiconf -s 3 or gnome's suspend and the dmesg
shows: acpi0: device_suspend failed.
I'm running Freebsd 8.0 amd64. My bios is up to date.
Intel core 2 quad with SMP on.
sysctl -a | grep cx_supported:
dev.cpu.0.cx_supported: C1/0
dev.cpu.1.cx_supported: C1/0
dev.cpu.2.cx_supported: C1/0
dev.cpu.3.cx_supported: C1/0
Also incase it helps:
sysctl -a | grep -i acpi:
kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) i8254(0)
dummy(-1000000)
kern.timecounter.hardware: ACPI-fast
kern.timecounter.tc.ACPI-fast.mask: 16777215
kern.timecounter.tc.ACPI-fast.counter: 4908315
kern.timecounter.tc.ACPI-fast.frequency: 3579545
kern.timecounter.tc.ACPI-fast.quality: 1000
debug.acpi.suspend_bounce: 0
debug.acpi.reset_clock: 1
debug.acpi.do_powerstate: 1
debug.acpi.acpi_ca_version: 20090521
debug.acpi.ec.timeout: 750
debug.acpi.ec.polled: 0
debug.acpi.ec.burst: 0
debug.acpi.batt.batt_sleep_ms: 0
debug.acpi.resume_beep: 0
hw.acpi.supported_sleep_state: S3 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S3
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: NONE
hw.acpi.suspend_state: S3
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.disable_on_reboot: 0
hw.acpi.handle_reboot: 0
hw.acpi.reset_video: 0
hw.acpi.cpu.cx_lowest: C1
machdep.acpi_timer_freq: 3579545
machdep.acpi_root: 1011072
machdep.idle: acpi
machdep.idle_available: spin, mwait, mwait_hlt, hlt, acpi,
dev.acpi.0.%desc: GBT GBTUACPI
dev.acpi.0.%driver: acpi
dev.acpi.0.%parent: nexus0
dev.acpi_sysresource.0.%desc: System Resource
dev.acpi_sysresource.0.%driver: acpi_sysresource
dev.acpi_sysresource.0.%location: handle=\_SB_.PCI0.PX40.SYSR
dev.acpi_sysresource.0.%pnpinfo: _HID=PNP0C02 _UID=1
dev.acpi_sysresource.0.%parent: acpi0
dev.acpi_sysresource.1.%desc: System Resource
dev.acpi_sysresource.1.%driver: acpi_sysresource
dev.acpi_sysresource.1.%location: handle=\_SB_.PCI0.PX40.PMIO
dev.acpi_sysresource.1.%pnpinfo: _HID=PNP0C02 _UID=2
dev.acpi_sysresource.1.%parent: acpi0
dev.acpi_sysresource.2.%desc: System Resource
dev.acpi_sysresource.2.%driver: acpi_sysresource
dev.acpi_sysresource.2.%location: handle=\_SB_.PCI0.EXPL
dev.acpi_sysresource.2.%pnpinfo: _HID=PNP0C02 _UID=4
dev.acpi_sysresource.2.%parent: acpi0
dev.acpi_sysresource.3.%desc: System Resource
dev.acpi_sysresource.3.%driver: acpi_sysresource
dev.acpi_sysresource.3.%location: handle=\_SB_.MEM_
dev.acpi_sysresource.3.%pnpinfo: _HID=PNP0C01 _UID=0
dev.acpi_sysresource.3.%parent: acpi0
dev.acpi_timer.0.%desc: 24-bit timer at 3.579545MHz
dev.acpi_timer.0.%driver: acpi_timer
dev.acpi_timer.0.%location: unknown
dev.acpi_timer.0.%pnpinfo: unknown
dev.acpi_timer.0.%parent: acpi0
dev.pci_link.0.%desc: ACPI PCI Link LNKA
dev.pci_link.0.%parent: acpi0
dev.pci_link.1.%desc: ACPI PCI Link LNKB
dev.pci_link.1.%parent: acpi0
dev.pci_link.2.%desc: ACPI PCI Link LNKC
dev.pci_link.2.%parent: acpi0
dev.pci_link.3.%desc: ACPI PCI Link LNKD
dev.pci_link.3.%parent: acpi0
dev.pci_link.4.%desc: ACPI PCI Link LNKE
dev.pci_link.4.%parent: acpi0
dev.pci_link.5.%desc: ACPI PCI Link LNKF
dev.pci_link.5.%parent: acpi0
dev.pci_link.6.%desc: ACPI PCI Link LNK0
dev.pci_link.6.%parent: acpi0
dev.pci_link.7.%desc: ACPI PCI Link LNK1
dev.pci_link.7.%parent: acpi0
dev.acpi_hpet.0.%desc: High Precision Event Timer
dev.acpi_hpet.0.%driver: acpi_hpet
dev.acpi_hpet.0.%location: unknown
dev.acpi_hpet.0.%pnpinfo: unknown
dev.acpi_hpet.0.%parent: acpi0
dev.acpi_button.0.%desc: Power Button
dev.acpi_button.0.%driver: acpi_button
dev.acpi_button.0.%location: handle=\_SB_.PWRB
dev.acpi_button.0.%pnpinfo: _HID=PNP0C0C _UID=0
dev.acpi_button.0.%parent: acpi0
dev.pcib.0.%desc: ACPI Host-PCI bridge
dev.pcib.0.%parent: acpi0
dev.pcib.2.%desc: ACPI PCI-PCI bridge
dev.pcib.3.%desc: ACPI PCI-PCI bridge
dev.pcib.4.%desc: ACPI PCI-PCI bridge
dev.pcib.5.%desc: ACPI PCI-PCI bridge
dev.pcib.6.%desc: ACPI PCI-PCI bridge
dev.pci.0.%desc: ACPI PCI bus
dev.pci.2.%desc: ACPI PCI bus
dev.pci.3.%desc: ACPI PCI bus
dev.pci.4.%desc: ACPI PCI bus
dev.pci.5.%desc: ACPI PCI bus
dev.pci.6.%desc: ACPI PCI bus
dev.atdma.0.%parent: acpi0
dev.attimer.0.%parent: acpi0
dev.atrtc.0.%parent: acpi0
dev.fpupnp.0.%parent: acpi0
dev.uart.0.%parent: acpi0
dev.ppc.0.%parent: acpi0
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%parent: acpi0
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%parent: acpi0
dev.cpu.2.%desc: ACPI CPU
dev.cpu.2.%parent: acpi0
dev.cpu.3.%desc: ACPI CPU
dev.cpu.3.%parent: acpi0
Thanks
Tim M
Tim Matthews
success:
http://lists.freebsd.org/pipermail/freebsd-acpi/2010-January/006251.html
Jung-uk Kim
The error message says one of the device drivers failed to suspend
properly. When that happens, acpi(4) refuses to suspend for "better
safer than sorry" reason. You can try one thing, though. Remove all
non-essential device drivers from kernel configuration and build a
bare minimum kernel, which is just enough to boot your machine. If
this kernel suspends successfully, then try adding one driver at a
time until you find a culprit.
Good luck.
Jung-uk Kim
Tim Matthews
>
> The error message says one of the device drivers failed to suspend
> properly. When that happens, acpi(4) refuses to suspend for "better
> safer than sorry" reason. You can try one thing, though. Remove all
> non-essential device drivers from kernel configuration and build a
> bare minimum kernel, which is just enough to boot your machine.
>
I have removed just about everything and made sure there wasn't anything
lying around in loader.conf too. The suspend still fails.
Is there anything else that can be done?
Thanks
Ian Smith
You could try turning on hw.acpi.verbose in sysctl.conf (I noticed it
was off), booting with verbose messages on, then looking at the messages
before, during and after attempting to suspend. This may show something
about some particular device that won't or can't suspend, that you could
then show us.
/var/run/dmesg.boot (verbose) may also contain some related clues.
cheers, Ian