Your message dated Thu, 27 Apr 2006 23:04:02 -0700 (PDT)
with message-id <[EMAIL PROTECTED]>
and subject line linux-2.6: no sound: codec_write 0: semaphore is not ready for
register
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-image-2.6.12-1-686-smp
Version: 2.6.12-1
Severity: normal
In all Debian kernel packages above 2.6.8, sound is completely broken on my
laptop. Trying to adjust volume settings gives me errors of this sort in the
kernel log:
Aug 6 04:57:27 mauritius kernel: codec_write 0: semaphore is not ready for
register 0x2
Aug 6 04:57:27 mauritius kernel: codec_write 0: semaphore is not ready for
register 0x2
Aug 6 04:57:27 mauritius kernel: codec_write 0: semaphore is not ready for
register 0x18
Aug 6 04:57:27 mauritius kernel: codec_write 0: semaphore is not ready for
register 0x18
Aug 6 04:57:27 mauritius kernel: codec_write 0: semaphore is not ready for
register 0x12
Aug 6 04:57:27 mauritius kernel: codec_write 0: semaphore is not ready for
register 0x12
Aug 6 04:57:27 mauritius kernel: codec_write 0: semaphore is not ready for
register 0x4
Aug 6 04:57:27 mauritius kernel: codec_write 0: semaphore is not ready for
register 0x4
No evidence that the mixer settings actually change. In any case, sound
apps hang when trying to open the sound device for output, so it hardly seems
to matter if the mixer works.
Sound device is, from lspci:
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R)
AC'97 Audio Controller (rev 02)
and lspci -n:
0000:00:1f.5 0401: 8086:24d5 (rev 02)
Under 2.6.8, the following modules are loaded:
snd_intel8x0m 20872 0
snd_intel8x0 37452 2
snd_ac97_codec 70884 2 snd_intel8x0m,snd_intel8x0
snd_pcm_oss 55912 1
snd_mixer_oss 20384 2 snd_pcm_oss
snd_pcm 102948 3 snd_intel8x0m,snd_intel8x0,snd_pcm_oss
snd_timer 27492 1 snd_pcm
snd_page_alloc 12008 3 snd_intel8x0m,snd_intel8x0,snd_pcm
gameport 5120 1 snd_intel8x0
snd_mpu401_uart 8640 1 snd_intel8x0
snd_rawmidi 26084 1 snd_mpu401_uart
snd_seq_device 8456 1 snd_rawmidi
I haven't checked yet how this list compares to what gets loaded under
2.6.12.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-686-smp
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.6.15-8
Steve has confirmed that the modules no longer conflict in 2.6.15-8, so
this bug is fixed.
Jurij Smakov [EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--- End Message ---
