kernel: 2.6.14-r2-gentoo as soon i upgraded the module-init-tools from 3.0-r2 to 3.2.1 it crashed all the sound player programs, using alsa (1.0.10): the program got <defunc> flag in the process list, and couldnt be killed. alsasound stop couldnt unload the alsa modules, since they were probaly busy with the programs. The worst is that i didnt get any error messages, the programs (mplayer 1.0-pre7-r1, xmms 1.2.10) simply crashed when started.
Same here. I get kernel oopses when loading sound drivers from alsa-driver. The newer module-init-tools and the alsa-driver ebuilds don't seem to get along at all.
Same here with alsa in kernel. Downgrading to 3.0-r2 makes it work again. Actually the snd-modules can
Same here with alsa in kernel. Downgrading to 3.0-r2 makes it work again. Actually the snd-modules can´t be loaded with look a bit like the the issues mentioned in the alsa-guide (http://www.gentoo.org/doc/en/alsa-guide.xml#doc_chap3_pre11) but isn´t resolved like it says.
*** Bug 121308 has been marked as a duplicate of this bug. ***
last i heard this was a kernel bug, try upgrading the kernel should never *oops* because of a *userspace* utility
It is probably bug in ALSA: media-sound/alsa-driver-1.0.11_rc3 With kernel 2.6.15-r4 it works but with when I have rebuilt alsa-driver it oopsed.
i'm inclined to blame alsa ... lemme know ;)
Does recent 1.0.11_rc5 fix this?
No, just checked with mod-3.2.1 and alsa-rc5 (on amd64) Unable to handle kernel NULL pointer dereference at 0000000000000282 RIP: <ffffffff88018385>{:snd:snd_register_device+60} PGD 26347067 PUD 2d94c067 PMD 0 Oops: 0000 [1] PREEMPT CPU 0 Modules linked in: snd_timer snd snd_page_alloc siimage fglrx agpgart rt2400 forcedeth it87 hwmon_vid eeprom i2c_isa i2c_nforce2 i2c_core nls_cp1250 nls_cp437 pl2303 usbserial Pid: 20188, comm: modprobe Tainted: P 2.6.15-gentoo-r7 #1 RIP: 0010:[<ffffffff88018385>] <ffffffff88018385>{:snd:snd_register_device+60} RSP: 0018:ffff810004fb9ef8 EFLAGS: 00010292 RAX: 0000000000000000 RBX: 0000000000000021 RCX: ffffffffffffffff RDX: 0000000000000000 RSI: 00000000000000d0 RDI: 0000000000000282 RBP: ffffffff8802c100 R08: ffffffff8802a268 R09: 0000000000000282 R10: ffff81003e81fd30 R11: 0000000000000246 R12: 0000000000000000 R13: ffffffffffffffff R14: 0000000000000282 R15: ffffffff8802bf20 FS: 00002aaaaaefad60(0000) GS:ffffffff803d4800(0000) knlGS:000000005612a820 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000282 CR3: 000000000528a000 CR4: 00000000000006e0 Process modprobe (pid: 20188, threadinfo ffff810004fb8000, task ffff81003f24c280) Stack: 0000000000000000 ffffffff8802a268 0000000000000000 ffff81003ea73e40 ffffffff8802c100 ffffffff803433f0 0000000000507fb0 0000000000401a50 000000000051b8f0 ffffffff8802e14c Call Trace:<ffffffff8802e14c>{:snd_timer:alsa_timer_init+332} <ffffffff80147273>{sys_init_module+231} <ffffffff8010e77e>{system_call+126} Code: f2 ae 48 f7 d1 48 8d 79 20 e8 bf 9e 13 f8 48 89 c5 b8 f4 ff RIP <ffffffff88018385>{:snd:snd_register_device+60} RSP <ffff810004fb9ef8> CR2: 0000000000000282
Still an issue with 1.0.13? CCing kernel as this might just be a kernel bug.
This is a crash purely in the ALSA module code
(that was in response to comment #8 -- not enough info has been provided in the other cases)
Latest ALSA and kernel - works.
(In reply to comment #9) works here too with latest kernels.
Considering fixed by UPSTREAM then.
