Hmm. What's up with this? 2341 ? D< 0:00 [kacpid_notify] 2342 ? D< 0:00 [kacpid_notify] 2343 ? D< 0:00 [kacpid_notify] 2344 ? D< 0:00 [kacpid_notify] 2345 ? D< 0:00 [kacpid_notify] 2346 ? D< 0:00 [kacpid_notify] 2347 ? D< 0:00 [kacpid_notify] ... (apparently about 300 of those processes, at which point the machine just hangs, because even root cannot start any new processes, and I couldn't actually get to debug this at all). What would it be waiting on, and why? This machine doesn't have any module support (at all), and I haven't booted a new kernel on it in quite a while, so this isn't necessarily new behaviour, but the last kernel I tried (which did _not_ have this problem, obviously) was in April (commit 6e5882cfa24e1456702e463f6920fc0ca3c3d2b8, to be exact). Now, that's 6000+ commits ago, so I'd rather not even bisect this, if somebody can come up with a more obvious explanation of why kacpid_notify would be started over and over and over again, only to always get stuck.. Linus - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
