Bug#659671: Does not load all modules requested by udev

[Ben Hutchings]

Package: kmod
Version: 3-1
Severity: serious

When using kmod on this system, not all the same modules are being
auto-loaded. In particular, iwl3945 does not get loaded and i915
doesn't always get loaded when udev starts (but is loaded by the X
server when that starts).

I'm attaching the lists of modules loaded by the initramfs (which
still contains module-init-tools 3.16-1), two different boots to
single-user mode with kmod, and a boot to single-user mode with
module-init-tools 3.16-1.

Ben.

-- System Information:
Debian Release: wheezy/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmod depends on:
ii libc6 2.13-26
ii libkmod1 3-1
ii lsb-base 3.2-28.1

kmod recommends no packages.

kmod suggests no packages.

[Marco d'Itri]

On Feb 13, Ben Hutchings <b...@decadent.org.uk> wrote:

> When using kmod on this system, not all the same modules are being

Please try 5 from experimental or http://www.bofh.it/~md/debian/ .

--
ciao,
Marco

[Ben Hutchings]

udevadm settle seems to hang. Judging by the accelerating fan, modprobe
was very busy doing *something*, but I kind of wanted my system back so
I didn't investigate further.

Ben.

--
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein

[Ben Hutchings]

On Mon, 2012-02-13 at 04:51 +0000, Ben Hutchings wrote:
> On Mon, 2012-02-13 at 00:36 +0100, Marco d'Itri wrote:
> > On Feb 13, Ben Hutchings <b...@decadent.org.uk> wrote:
> >
> > > When using kmod on this system, not all the same modules are being
> > Please try 5 from experimental or http://www.bofh.it/~md/debian/ .
>
> udevadm settle seems to hang. Judging by the accelerating fan, modprobe
> was very busy doing *something*, but I kind of wanted my system back so
> I didn't investigate further.

It seems I can break out of this with ^C, but that leaves a couple of
modprobe processes still busy-looping.

The problem seems to be related to sound modules, as the processes left
around were both 'modprobe snd-ioctl32' and the real sound driver
(snd-hda-intel) was not loaded.

I suspect that this configuration line from
/etc/modprobe.d/alsa-base.conf somehow triggers the bug:

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; }