I just installed the Debian 2.6.18 kernel package and I noticed that it
repeatedly tries to load a major 442 module alias, which appears to be
used by the usb_endpoint devices.
Does anybody know why? I am not even using the USB ports.
md@bongo:~$uname -a
Linux bongo 2.6.18-1-686 #1 SMP Sat Oct 21 17:21:28 UTC 2006 i686 GNU/Linux
md@bongo:~$while sleep 0.1; do ps axf|grep modprob[e]; done
6424 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442_2049
6429 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442_2049
6438 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442
6447 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442_2048
6460 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442
6473 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442_8192
6487 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442
6500 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442_0
6517 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442
6557 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442_4096
6562 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442_4096
6571 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442
6582 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442
6595 ? R< 0:00 \_ /sbin/modprobe -q -- char_major_442_2051
[...]
--
ciao,
Marco
Am Mittwoch, 25. Oktober 2006 12:20 schrieb Marco d'Itri:
> I just installed the Debian 2.6.18 kernel package and I noticed that it
> repeatedly tries to load a major 442 module alias, which appears to be
> used by the usb_endpoint devices.
> Does anybody know why? I am not even using the USB ports.
grep 442 /etc/modprobe.conf
HTH
Eike
On Wed, Oct 25, 2006 at 12:20:30PM +0200, Marco d'Itri wrote:
> I just installed the Debian 2.6.18 kernel package and I noticed that it
> repeatedly tries to load a major 442 module alias, which appears to be
> used by the usb_endpoint devices.
> Does anybody know why? I am not even using the USB ports.
It doesn't matter if you are using them or not, they are being created
by the usb core for the next-version of usbfs. They currently are not
hooked up to anything properly, but people are working on them to fix
that soon.
And the number is just a placeholder, it's not a reserved major number.
As for what is trying to load the module, I have no idea, it must be
some userspace tool...
thanks,
greg k-h
On Oct 25, Greg KH <[email protected]> wrote:
> As for what is trying to load the module, I have no idea, it must be
> some userspace tool...
Found it... I had this experimental udev rule which puts the devices in
/dev/bus/usb/ and pcscd keeps scanning the directory every second
looking for Cthulhu knows what:
SUBSYSTEM=="usb_endpoint", PROGRAM="/bin/sh -c 'K=%k; E=$${K#*_}; K=$${K#usbdev}; K=$${K%%%%_*}; printf bus/usb/%%03i/%%03i_%%s $${K%%%%.*} $${K#*.} $$E'", \
NAME="%c"
--
ciao,
Marco