Lucas De Marchi
2013-07-16 06:42:35 UTC
Hello,
My x86_64 systems has some trouble loading some ALSA snd-* modules since
the upgrade to 3.10.[01]: Several automatic modprobe calls hang, but
loading snd-intel-hda and snd-audio-usb by hand still works.
Not a known problem to me, at least. Perhaps it's a dep loop somehow.My x86_64 systems has some trouble loading some ALSA snd-* modules since
the upgrade to 3.10.[01]: Several automatic modprobe calls hang, but
loading snd-intel-hda and snd-audio-usb by hand still works.
these install commands. Did they change besides the kernel upgrade?
[
Not really related to this, but... people/distros should stop using
install commands for things like this. By using softdeps kmod is smart
enough to detect and (possibly) break loops. With install commands it
can't because it has no idea what the install command will do.
]
...
1071 ? S 0:00 sh -c /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet snd
1080 ? D 0:00 \_ /sbin/modprobe --quiet snd-seq
This was first, and it's waiting. Which means it must be doing1071 ? S 0:00 sh -c /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet snd
1080 ? D 0:00 \_ /sbin/modprobe --quiet snd-seq
snd_seq_oss 33717 1 - Loading 0xffffffffa041b000
install snd_seq modprobe --ignore-install snd-seq $CMDLINE_OPTS && {
modprobe --quiet snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
Perhaps in the tangle of modprobe install commands somewhere this gets
invoked?
Weird... this is coming from a request_module(). Greping... thisinvoked?
# ps axf
460 ? S 0:00 \_ [kworker/u8:3]
1087 ? S 0:00 | \_ [kworker/u8:3]
1092 ? S 0:00 | \_ /sbin/modprobe -q -- snd-seq-client-14
460 ? S 0:00 \_ [kworker/u8:3]
1087 ? S 0:00 | \_ [kworker/u8:3]
1092 ? S 0:00 | \_ /sbin/modprobe -q -- snd-seq-client-14
should only be coming from
git grep request_module | grep snd-seq-client
sound/core/seq/seq_clientmgr.c: request_module("snd-seq-client-%i",
Philipp, which kernel are you upgrading from? I don't see anything to
blame in the changes for the past releases. Any chance a bad entry in
your .conf was added too? You may want to paste the output of modprobe
-c, at least until "# End of configuration files. Dumping indexes
now:"
On my systems, that's snd-seq-dummy, which depends on snd_seq. Which,
in fact, is already loaded.
Lucas, any clues?
I don't think I could help, but we need more data, like the ones above.in fact, is already loaded.
Lucas, any clues?
Lucas De Marchi