Re: Kernel warning messages when insmodding unix.o
On Thu, 2003-07-10 at 17:16, Frank Murphy wrote:
> > Well, init is /bin/sh in this scenario, so you're saying the warnings
> > also appear if you don't type anything at the shell prompt? If not, the
> > idea is to start the /etc/rcS.d/S* scripts one by one and notice after
> > which one(s) the warnings appear.
> Exactly. In fact, the unix.o warnings are printed before the init shell prompt
> and the mousedev warnings just after. But I don't type anything. It seems
> that these warnings are not coming from the rcS.d scripts.
> > > I get another complaint with hid.o and a missing mousedev module (which
> > > makes sense because moudev.o is only for PS/2 mice, I believe; however,
> > > before init starts there's a log "mice: PS/2 mouse device common for all
> > > mice").
> > Which doesn't sound like it's only for PS/2 mice, does it? :)
> Actually, I find the log confusing. But perhaps that's because the mousedev
> module is not currently built for Debian PPC kernels,
It's built in, isn't it?
grep MOUSEDEV= /boot/config-`uname -r`
> and I'm looking for some reason that it's getting modprobed.
mousedev is loaded and in use here, I guess it's the driver behind
/dev/input/mice and friends. My guess is /sbin/hotplug tries to load it
when the kernel generates a hotplug event for the mouse (or trackpad?).
> > The input related module(s) could be loaded by something like hotplug.
> The /etc/init.d/hotplug script hasn't been run at this point. Though I think
> that the kernel might call /sbin/hotplug when it gets a hotplug event,
Indeed, it does.
> though it only loads hid at this point, not all the unix.o module (I'd guess).
My only idea for the unix module is that something tries to access a
UNIX socket, and the kernel autoloads it.
Maybe all the problems are caused by or at least related to the /proc
Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer