| Summary: | Regression: Starting with 1.23 ACPI shutdown stopped working within VirtualBox | ||
|---|---|---|---|
| Product: | Busybox | Reporter: | Axel Fontaine <axel> |
| Component: | Other | Assignee: | unassigned |
| Status: | NEW --- | ||
| Severity: | normal | CC: | busybox-cvs |
| Priority: | P5 | ||
| Version: | 1.23.x | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
Axel Fontaine
2015-12-09 15:47:18 UTC
By stopped working I meant: has no effect anymore, the instance keeps running instead of shutting down as expected you probably need to trace this a bit for us to see what command is changing in behavior if you don't mind using git, the bisect operator might help speed things up This is the only recent commit to halt.c after 4 years: https://git.busybox.net/busybox/commit/init/halt.c?id=86a7f18f211af1abda5c855d2674b0fcb53de524 Could that be the cause? The only other suspect could be: https://git.busybox.net/busybox/commit/init/init.c?id=da9212667c99f2f2121747c4715d067deb7c155b Not much else happened within https://git.busybox.net/busybox/tree/init in the affected timeframe A final suspect could be https://git.busybox.net/busybox/commit/util-linux/acpid.c?id=bbf1e3c144c1ee93409a0e0546cb56b34eccfcfd you have the system that's failing, so it should be pretty easy to test each one of those commits to see if they fix your system, and then you can let us know This issue may be similar to Bug 12071, which may be caused by https://git.busybox.net/busybox/commit/init/init.c?id=2bba9ad67a917de2624d427c8c107ce3e2d3d085 In addition, someone reported it in busybox github mirror: https://github.com/mirror/busybox/commit/2bba9ad67a917de2624d427c8c107ce3e2d3d085 |