jaya@xxxxxxx wrote:
>
> Hi Jeff,
>
> > (We've got a bunch of SGI Linux boxen running SGI's version of RedHat)
>
> This particular one looks like a 330 with ProPack 1.3-VW. :-)
> I think the temporary workaround is to remove rmmod -as from
> /etc/cron.d/kmod. I think you have done this.
Yup.
> > looks to me like dmdaemon is using those kernel modules but doesn't have
> > the appropriate things open so rmmod sees those modules as not being in
>
> I don't think there is an issue with dmdaemon. What happens is that
> when dmdaemon starts up on linux, the loading of the ossaudio dmmodule
> causes dmdaemon to open the appropriate /dev/ entry to allow queries
> on the ossaudio device. Once it's done with the queries, it closes
> these opened file handles since it dosen't need them anymore (and it
> should be able to do this without worry). Nor is it a bug in rmmod.
> The problem (afaict) lies in the ALSA modules. One note is that I
> don't see this problem on my sgi 550 running 1.3-VW + 1.4 (it has a
> different version of the ALSA modules and kernel).
>
> dmdaemon causes the loading of the same modules that a basic audio app
> would. Could you try repeating the experiment with mpg123 (run mpg123,
> exit, rmmod, rmmod)? Also, there's been a couple of revisions of ALSA
> since the 0.59 version that shipped with 1.3-VW. I am told that there
> will be a sw update for 230/330/550 soon with a new kernel, new ALSA
> drivers, new gfx drivers so I'll get the appropriate people to help us
> check that this issue dosen't happen on a 330 with said
> configuration.
Yup, rmmod hangs after running mpg123 and exiting. Thanks for the
help. And yes, I am running an SGI 330.
|