ALSA bugs with 2.6.12-rc1
It seems that 2.6.12-rc1 introduced an ALSA bug generating an oops for a null pointer.
codec_semaphore: semaphore is not ready [0x1][0x300300] codec_read 0: semaphore is not ready for register 0x2c
Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c01d7746 *pde = 00000000 Oops: 0002 [#1] PREEMPT Modules linked in: orinoco_cs orinoco hermes pcmcia yenta_socket rsrc_nonstatic pcmcia_core vfat fat nls_base i2c_sensor i2c_core eth1394 ohci1394 ieee1394 i8k CPU: 0 EIP: 0060:[<c01d7746>] Not tainted VLI EFLAGS: 00010202 (2.6.12-rc1)
EIP is at memcpy+0x1e/0x39
eax: 00000010 ebx: e7608180 ecx: 00000004 edx: 00000000
esi: e13d1ee4 edi: 00000000 ebp: bf924390 esp: e13d1eb4
ds: 007b es: 007b ss: 0068
Process artsd (pid: 11880, threadinfo=e13d1000 task=e1436590)
Stack: ffffffea ffffffea e13d1ef4 c02b8793 00000000 e13d1ee4 00000010 e7608180
c02b954d e7608180 e13d1ee4 00000050 00000006 00000000 00000000
00000000
00000005 00000001 00000000 00000000 00008002 00000000 00000000
00000000
Call Trace:
[<c02b8793>] snd_timer_user_append_to_tqueue+0x40/0x49
[<c02b954d>] snd_timer_user_params+0x236/0x245
[<c016f152>] do_ioctl+0x9a/0xa9
[<c016f2ef>] vfs_ioctl+0x65/0x1e1
[<c015bc34>] get_unused_fd+0x2c/0xd2
[<c016f4b0>] sys_ioctl+0x45/0x6d
[<c0102f87>] sysenter_past_esp+0x54/0x75
Code: fd 31 c0 c3 31 d2 b8 f2 ff ff ff c3 90 83 ec 0c 8b 44 24 18 8b 54 24 10 89 74 24 04 89 c1 89 7c 24 08 8b 74 24 14 c1 e9 02 89 d7 <f3> a5 a8 02 74 02 66 a5 a8 01 74 01 a4 89 d0 8b 74 24 04 8b 7ccodec_semaphore: semaphore is not ready [0x1][0x300300] codec_read 1: semaphore is not ready for register 0x54codec_semaphore: semaphore is not ready [0x1][0x300300] codec_write 1: semaphore is not ready for register 0x54
This happens on multiple machines, 32b and 64bit. I'll be happy to provide further information if needed.
-david
Quoted 10 lines · David Ford
It seems that 2.6.12-rc1 introduced an ALSA bug generating an oops for a null pointer.
codec_semaphore: semaphore is not ready [0x1][0x300300]codec_read0: semaphore is not ready for register0x2cUnable to handle kernel NULL pointer dereference at virtual address00000000
This happens on multiple machines, 32b and 64bit. I'll be happy to provide further information if needed.
This only happens when you mismatch your kernel and alsa-lib versions, e.g. running alsa-lib-1.0.9-rc2 with alsa-1.0.8 in-kernel drivers, or possibly vice-versa.
Daniel
At Mon, 04 Apr 2005 18:08:43 +0100,
Quoted 10 lines · Daniel Drake
Quoted 8 lines · David Ford
It seems that 2.6.12-rc1 introduced an ALSA bug generating an oops for a null pointer.
codec_semaphore: semaphore is not ready [0x1][0x300300]codec_read0: semaphore is not ready for register0x2cUnable to handle kernel NULL pointer dereference at virtual address00000000
Quoted 6 lines
Quoted 2 lines
This happens on multiple machines, 32b and 64bit. I'll be happy to provide further information if needed.
This only happens when you mismatch your kernel and alsa-lib versions, e.g. running alsa-lib-1.0.9-rc2 with alsa-1.0.8 in-kernel drivers, or possibly vice-versa.
Only the former case (kernel < lib).
It's already fixed in linux-sound bk tree. The relevant patch is below. The patch was already submitted to stable, too.
Takashi
# This is a BitKeeper generated diff -Nru style patch. #
# ChangeSet
# 2005/03/22 09:01:11+01:00 [email protected]
# [ALSA] Fix Oops with timer notifying
#
# Timer Midlevel
# Fixed Oops with timer notifying after TIMER_TREAD ioctl.
#
# Signed-off-by: Takashi Iwai <[email protected]>
#
# sound/core/timer.c # 2005/03/15 04:25:51+01:00 [email protected] +2 -1 # [ALSA] Fix Oops with timer notifying # # D:2005/03/15 11:25:51 # C:Timer Midlevel # F:core/timer.c:1.65->1.66 # L:Fixed Oops with timer notifying after TIMER_TREAD ioctl. # Signed-off-by: Takashi Iwai <[email protected]> # diff -Nru a/sound/core/timer.c b/sound/core/timer.c --- a/sound/core/timer.c 2005-04-04 19:25:12 +02:00 +++ b/sound/core/timer.c 2005-04-04 19:25:12 +02:00 @@ -1117,7 +1117,8 @@ if (tu->qused >= tu->queue_size) { tu->overrun++; } else { - memcpy(&tu->queue[tu->qtail++], tread, sizeof(*tread)); + memcpy(&tu->tqueue[tu->qtail++], tread, sizeof(*tread)); + tu->qtail %= tu->queue_size; tu->qused++; } }
Quoted 9 lines · Daniel Drake
Quoted 8 lines · David Ford
It seems that 2.6.12-rc1 introduced an ALSA bug generating an oops for a null pointer.
codec_semaphore: semaphore is not ready [0x1][0x300300]codec_read0: semaphore is not ready for register0x2cUnable to handle kernel NULL pointer dereference at virtual address00000000
Quoted 6 lines
Quoted 2 lines
This happens on multiple machines, 32b and 64bit. I'll be happy to provide further information if needed.
This only happens when you mismatch your kernel and alsa-lib versions, e.g. running alsa-lib-1.0.9-rc2 with alsa-1.0.8 in-kernel drivers, or possibly vice-versa.
Are you saying the userspace interface of the ALSA kernel drivers has incompatible changes between minor versions of ALSA?
If this is true, that's a serious bug.
Quoted 1 line
Daniel
cu
Adrian
Signature · 12 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=clickQuoted 9 lines · Daniel Drake
Quoted 8 lines · David Ford
It seems that 2.6.12-rc1 introduced an ALSA bug generating an oops for a null pointer.
codec_semaphore: semaphore is not ready [0x1][0x300300]codec_read0: semaphore is not ready for register0x2cUnable to handle kernel NULL pointer dereference at virtual address00000000
Quoted 6 lines
Quoted 2 lines
This happens on multiple machines, 32b and 64bit. I'll be happy to provide further information if needed.
This only happens when you mismatch your kernel and alsa-lib versions, e.g. running alsa-lib-1.0.9-rc2 with alsa-1.0.8 in-kernel drivers, or possibly vice-versa.
Are you saying the userspace interface of the ALSA kernel drivers has incompatible changes between minor versions of ALSA?
If this is true, that's a serious bug.
Quoted 1 line
Daniel
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 13 lines · Adrian Bunk
Quoted 12 lines · Daniel Drake
Quoted 10 lines · David Ford
It seems that 2.6.12-rc1 introduced an ALSA bug generating an oops for a null pointer.
codec_semaphore: semaphore is not ready [0x1][0x300300]codec_read0: semaphore is not ready for register0x2cUnable to handle kernel NULL pointer dereference at virtual address00000000
This happens on multiple machines, 32b and 64bit. I'll be happy to provide further information if needed.
Quoted 8 lines
Quoted 3 lines
This only happens when you mismatch your kernel and alsa-lib versions, e.g. running alsa-lib-1.0.9-rc2 with alsa-1.0.8 in-kernel drivers, or possibly vice-versa.
Are you saying the userspace interface of the ALSA kernel drivers has incompatible changes between minor versions of ALSA?
If this is true, that's a serious bug.
Nope, but newer alsa-lib use an ALSA timer API feature which was not well debugged. This oops should be fixed in 2.6.12-rc2 and older libraries will work with newer kernels as well.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click