From: Erik Steffl <steffl@bigfoot.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: modprobe -v snd-seq-oss freezes (sb live! kernel 2.6.5)
Date: Mon, 05 Jul 2004 03:03:08 -0700 [thread overview]
Message-ID: <40E9275C.2010707@bigfoot.com> (raw)
alsa used to work on my system, I didn't change anything I think
might be related and suddenly the modprobe -v snd-seq-oss freezes (does
not return, cannot be interrupted either but the rest of the system
(including audio and alsa native midi) works OK).
system:
debian unstable
kernel 2.6.5 (with alsa)
I did not change kernel or modules (I checked and there are no
new/changed files under /lib/modules/2.6.5) yet suddenly (after reboot)
the oss sequencer cannot be loaded. There are no (related) messages in
/var/log/syslog.
jojda:/home/erik# modprobe -v snd-seq-oss
insmod /lib/modules/2.6.5/kernel/sound/core/seq/snd-seq.ko
insmod /lib/modules/2.6.5/kernel/sound/core/seq/snd-seq-midi-event.ko
insmod /lib/modules/2.6.5/kernel/sound/core/seq/oss/snd-seq-oss.ko
and the modprobe does not exit, it just sits there. udev creates
devices (see below) but there are not usable, e.g.:
jojda:/var/log# sfxload /data/music/soundfont/creative/8MBGMSFX.SF2
/dev/sequencer: No such device
udev says (in daemon.log):
Jul 5 01:18:24 jojda udev[2821]: configured rule in
'/etc/udev/rules.d/udev.rules' at line 38 applied, 'midiC0D2' becomes
'snd/%k'
Jul 5 01:18:24 jojda udev[2821]: creating device node '/dev/snd/midiC0D2'
Jul 5 01:18:25 jojda udev[2791]: configured rule in
'/etc/udev/rules.d/udev.rules' at line 36 applied, 'hwC0D2' becomes 'snd/%k'
Jul 5 01:18:25 jojda udev[2791]: creating device node '/dev/snd/hwC0D2'
Jul 5 01:18:25 jojda udev[2798]: configured rule in
'/etc/udev/rules.d/udev.rules' at line 38 applied, 'midiC0D1' becomes
'snd/%k'
Jul 5 01:18:25 jojda udev[2798]: creating device node '/dev/snd/midiC0D1'
Jul 5 01:18:25 jojda udev[2768]: configured rule in
'/etc/udev/rules.d/udev.rules' at line 40 applied, 'seq' becomes 'snd/%k'
Jul 5 01:18:25 jojda udev[2768]: creating device node '/dev/snd/seq'
Jul 5 01:18:25 jojda udev[2775]: creating device node '/dev/sequencer'
Jul 5 01:18:25 jojda udev[2782]: creating device node '/dev/sequencer2'
Jul 5 01:18:25 jojda udev[2805]: creating device node '/dev/amidi'
Jul 5 01:18:25 jojda udev[2812]: creating device node '/dev/admmidi'
Jul 5 01:20:22 jojda ntpd[2392]: kernel time sync enabled 0001
any ideas on how to troubleshoot this?
TIA,
erik
reply other threads:[~2004-07-05 10:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40E9275C.2010707@bigfoot.com \
--to=steffl@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox