Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

Trenton D. Adams
2009-04-07T20:53:27Z

On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
>> <stefanr@s5r6.in-berlin.de> 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".)

I run dispatch-conf every time I update. It did not set it to no by
default. I do see the option though.

>
>> 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.

I don't know really. It worked before, now it doesn't. But, now I'm
recalling something you said earlier. They are being done in the
wrong order. The gentoo bug mentions the correct order. I hadn't
realized that.

>
> 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?

It could be. I will try it out when I get home from work, and get
back to you. That would be cool if it was a simple init script
problem. Cause then I don't have to do anymore git bisects. ;)

> --
> Stefan Richter
> -=====-=-=== -=-= -==-=
> http://arcgraph.de/sr/
>