What the hell is /etc/modutils/devfsd? More Debian tricks?
[...]
> > You must have a bogus /etc/devfsd.conf or /etc/modules.devfs file for
> > module autoloading not to work.
>
> I had commented out the .* MODLOAD, it worked before that. I uncommented the
> .* and it still does not work, something else must have changed.
>
> > I don't know what a "perms" file is. I know Debian uses some
> > convoluted directory tree for devfsd configuration, but frankly, I
> > don't want to know about that. If you have one of these monstrosities,
> > please collapse them all into a single /etc/devfsd.conf file a report
> > based on that.
>
> OK. I have nothing but REGISTER PERMISSIONS for floppy in devfsd.conf.
Argh! Let me spell it out: I want you to collapse all devfsd
configuration files into a single file, and throw the stuff in
directories away. And I also want you to do the same for modutils
configuration files. I don't want you to edit out stuff that you think
isn't relevant. I want the whole bloody lot so I can see the context.
Once you've stripped down the configuration to something simple, check
if the Oops still happens. If so, decode it with ksymoops and send it.
Hm. And also send the complete output of dmesg. No editing.
> > Hm. Please try a virgin 2.4.9 kernel with CONFIG_DEVFS_FS=n and try
> > again. I have this feeling that I'm chasing someone else's bug...
>
> OK, done. I did not get the oops with DEVFS turned off (in 2.4.9).
Interesting. But I need those collapsed files. I have no desire to
figure out the subtle effects that can be generated by Debian's
configuration system.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/