Re: A module bug in 2.2.1?
H.J. Lu (hjl@lucon.org)
Thu, 4 Feb 1999 07:00:59 -0800 (PST)
>
> >Hi,
> >
> >I made unix domain socket as a module in 2.2.1. When I booted up, I
> >got so many
> >
> >insmod: a module named /lib/modules/2.2.1/misc/unix already exists
> >
> >Any ideas?
>
> kmod in the kernel is trying to demand load unix domain sockets with
> 'modprobe -s -k unix'. modprobe gets some error. Because modprobe
> was given "-s", it calls syslog to record the error. syslog tries to
> use a unix domain socket, causing the kernel to again 'modprobe -s -k unix'
> again, continuing the recursive cycle.
>
> I am not sure why you are getting an error in the first place though,
> especially that error. Do you perhaps have a custom module of your own
> named "unix"?
>
I upgraded to modutils 2.1.121. This message is gone. Now I get
request_module[net-pf-1]: fork failed, errno 11
NET4: Unix domain sockets 1.0 for Linux NET4.0.
during the boot. I guess the bug may be in kernel and modutils. The
"unix" module is used by many programs. Everyone tries to load the
same thing at the same time. I will take a look to see if I can
fix it.
H.J.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/