Issue #2232 has been updated by swildner.
One more comment (unrelated to the actual issue): ACPI_LV_DEBUG was removed in 2009, and was only in the manual page still when this bug was filed. So the reason for the box crashing on boot was more likely one the ACPI we had at the time was having (trying to handle an unknown level) than a hint at an actual error caught by it (because it was already no longer existing in the code then). Trying to set acpi.debug.level to ACPI_LV_ERROR on a current system does not result in a crash. It boots and the acpi.debug.level sysctl shows "NONE", as it should, because it's an unknown level. Regards Sascha ---------------------------------------- Bug #2232: acpi - system cannot reboot or power down - 2.13.0.336.gacd31-DEVELOPMENT http://bugs.dragonflybsd.org/issues/2232#change-12036 * Author: ak * Status: Closed * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- Versions: Workstation: Lenovo Thinkcentre M58p DragonFlyBSD: v2.13.0.336.gacd31-DEVELOPMENT X86_64_GENERIC x86_64 ######### Problem Overview: My system cannot reboot or power down using ACPI. It stops after the following: Syncing disks… done Uptime: 11m24s I've tried with the commands: shutdown -p now shutdown -r now reboot power down and reboot work okay with FreeBSD 9.0 RC1 ######### ACPI info from sysctl: hw.acpi.power_button_state: S5 dfbsdp# sysctl -a | grep -i acpi kern.cputimer.select: HPET ACPI-safe24 i8254_timer2 dummy debug.acpi.level: NONE debug.acpi.layer: NONE debug.acpi.suspend_bounce: 0 debug.acpi.do_powerstate: 1 debug.acpi.acpi_ca_version: 20110211 debug.acpi.ec.timeout: 750 debug.acpi.ec.polled: 0 debug.acpi.ec.burst: 0 debug.acpi.semaphore_debug: 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: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 1 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 1 hw.acpi.reset_video: 1 hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu0.cx_supported: C1/1 C2/1 hw.acpi.cpu0.cx_lowest: C1 hw.acpi.cpu0.cx_usage: 100.00% 0.00% last 5000us machdep.acpi_timer_freq: 3579545 machdep.acpi_root: 1009904 ######### dfbsdp# acpiconf -s S5 acpiconf: invalid sleep type (5) ######### # acpidump -dt > out.asl Output from "iasl out.asl": your.asl 1264: Method (WQA0, 1, NotSerialized) Warning 1088 - ^ Not all control paths return a value (WQA0) your.asl 2122: And (CAPB, 0xFFFFFFFC) Warning 1106 - ^ Result is not used, operator has no effect your.asl 2123: Or (CAPB, 0x00) Warning 1106 - ^ Result is not used, operator has no effect your.asl 2290: DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, Error 4123 - ^ Min/Max/Length/Gran are all zero, but no resource tag your.asl 2926: Name (NATA, Package (0x03) Remark 5048 - ^ Initializer list shorter than declared package length your.asl 3386: Or (0x03, PARM) Warning 1106 - ^ Result is not used, operator has no effect your.asl 9648: Method (_WAK, 1, NotSerialized) Warning 1081 - ^ Reserved method must return a value (Integer/Package required for _WAK) ASL Input: your.asl - 11164 lines, 411038 bytes, 4585 keywords Compilation complete. 1 Errors, 5 Warnings, 1 Remarks, 1259 Optimizations ######### Followed the debug instructions for acpi in http://www.dragonflybsd.org/docs/handbook/handbook-acpi-debug/ but cannot set the debug layers/levels # cd /sys/dev/acpica5 && make clean && make ACPI_DEBUG=1 # mv acpi.ko /boot/kernel Adding the below to /boot/loader.conf causes a crash during boot. The error is "Fail trap 12: page fail while in kernel mode" and then enters DD: debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS" debug.acpi.level="ACPI_LV_ERROR" Adding those options using sysctl causes the system to hang (although I can turn on and off num lock on the keyboard in this state) ######### Attached dmesg and messages after verbose boot ---Files-------------------------------- dmesg-after-boot (106 KB) messages (173 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account