Trenton D. Adams wrote: > On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter > <stefanr@xxxxxxxxxxxxxxxxx> wrote: >>>> http://bugs.gentoo.org/show_bug.cgi?id=253535 >> Interdependencies between ALSA modules have changed. The Gentoo init >> scripts attempted to unload them in an order which deadlocked modprobe >> due to dependencies. The fix for Gentoo is to just not unload the >> modules on system shutdown. My Gentoo/amd64 Mac mini was affected by >> this too; fixed by userland update. >> > > While that is interesting, I am not seeing that problem on my Gentoo > box (the macbook), which is completely up-to-date. 2.6.28 works, and > 2.6.29 doesn't. Same init scripts, different kernels. Note that the respective update changed /etc/conf.d/alsasound (a local configuration file) to include UNLOAD_ON_STOP="no" KILLPROC_ON_STOP="no" This change by update is not activated by a mere emerge; one needs to incorporate that change with dispatch-conf or an equivalent method. (Or simply edit the file to have these variables set to "no".) > And sure, I could put a comment on the rmmod, in the init script, but > IMO that would be a hack around a _bug_. Which is fine for me. But, > is it worth leaving the issue in the kernel? Is it a kernel issue if a script attempts to unload a busy module, then fails to proceed? I wouldn't think so. But more importantly, is this init scripts related bug really what's happening at your system? Or do you actually experience an entirely different bug? -- Stefan Richter -=====-=-=== -=-= -==-= http://arcgraph.de/sr/ -- 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
