Skip to contentSkip to conversation

2.6.12: codec_semaphore: semaphore is not ready

DISCUSSION Rafael Rodríguez 5 participants 6 messages Jun 19, 2005 – Jun 20, 2005

lore
Share & tools
lore
#0 lore raw

Hi. Since I upgraded to 2.6.12, i get messages like

codec_semaphore: semaphore is not ready [0x1][0x 301300]
codec_write 1: semaphoreis not ready for register 0x54

_randomly_ (meaning that in some boots it shows up, but in others doesn't) in some init scripts (for example, alsa).

It's an HP pavilion zv5000 (amd64 laptop). Please tell me which more info may I supply to trace this. But I repeat, it's not _always_ reproducible.

Regards,

Rafael Rodríguez

#1 lore raw
Quoted 6 lines · Rafael Rodríguez

Hi. Since I upgraded to 2.6.12, i get messages like

codec_semaphore: semaphore is not ready [0x1][0x 301300]
codec_write 1: semaphoreis not ready for register 0x54

Quoted 6 lines

_randomly_ (meaning that in some boots it shows up, but in others doesn't) in some init scripts (for example, alsa).

It's an HP pavilion zv5000 (amd64 laptop). Please tell me which more info may I supply to trace this. But I repeat, it's not _always_ reproducible.

Just to let you know that you are not alone, I get the same messages. I'm too busy getting ready for a trip to Europe, I haven't had time to look further into this, otherwise I would. But I would like to let others know that this isn't just happening to one person.

-- Steve

#2 lore raw
In reply to Rafael Rodríguez

At Sun, 19 Jun 2005 14:02:02 +0100,

Quoted 9 lines · Rafael Rodríguez

Hi. Since I upgraded to 2.6.12, i get messages like

codec_semaphore: semaphore is not ready [0x1][0x 301300]
codec_write 1: semaphoreis not ready for register 0x54

_randomly_ (meaning that in some boots it shows up, but in others doesn't) in some init scripts (for example, alsa).

This comes from either snd-intel8x0 or snd-intel8x0m. You can see the driver name when CONFIG_SND_DEBUG=y is set.

If it's snd-intel8x0m (modem), you can ignore it unless you use the drvier indeed. If it's the former one (audio), it might be an ACPI problem. Try to tune acpi/pci boot option.

Takashi

#3 lore raw
Quoted 3 lines · Takashi Iwai

If it's snd-intel8x0m (modem), you can ignore it unless you use the drvier indeed. If it's the former one (audio), it might be an ACPI problem. Try to tune acpi/pci boot option.

Removed the snd-intel8xm, the message hasn't appeared again. So it seems that can be safely ignored (at least by me).

Thank you very much,

Rafael Rodríguez

#4 lore raw
Quoted 7 lines · Rafael Rodríguez
Quoted 3 lines · Takashi Iwai

If it's snd-intel8x0m (modem), you can ignore it unless you use the drvier indeed. If it's the former one (audio), it might be an ACPI problem. Try to tune acpi/pci boot option.

Removed the snd-intel8xm, the message hasn't appeared again. So it seems that can be safely ignored (at least by me).

I've found that my snd-intel8x0m modem works fine despite the codec_semaphore warnings, so I think it can be ignored by the majority. This also isn't a 2.6.12 problem, it's been happening for ages.

Signature · 8 lines
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/CSim Undergraduate
contact:    1F2 55 South Clerk Street,
            Edinburgh. EH8 9PP.
#5 lore raw
Quoted 4 lines · Alistair John Strachan

I've found that my snd-intel8x0m modem works fine despite the codec_semaphore warnings, so I think it can be ignored by the majority. This also isn't a 2.6.12 problem, it's been happening for ages.

Yes, and hopefully this warning is fixed already in ALSA CVS.

Sasha.