From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000311]: error messages: boot process, application start
Date: Thu, 24 Nov 2005 10:06:18 +0100 [thread overview]
Message-ID: <1e5773a358af10cbb0c92d37c3cd0965@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=311>
======================================================================
Reported By: phil
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 311
Category: PCI - intel8x0
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Distribution: Debian sid
Kernel Version: vanilla 2.6.5
======================================================================
Date Submitted: 05-27-2004 15:00 CEST
Last Modified: 11-24-2005 10:06 CET
======================================================================
Summary: error messages: boot process, application start
Description:
Everytime I boot my machine I get the following error code:
PCI: Enabling device 0000:00:1f.5 (0005 -> 0007)
PCI: Setting latency timer of device 0000:00:1f.5 to 64
ALSA sound/pci/intel8x0.c:596: codec_semaphore: semaphore is not ready
[0x1][0x700300]
ALSA sound/pci/ac97/ac97_codec.c:1868: MC'97 1 converters and GPIO not
ready (0xff00)
ALSA sound/pci/intel8x0.c:596: codec_semaphore: semaphore is not ready
[0x1][0x700300]
intel8x0_measure_ac97_clock: measured 49475 usecs
intel8x0: clocking to 48000
And the following one after starting frozen-bubble:
ALSA sound/core/seq/oss/seq_oss_init.c:213: no device found
ALSA sound/pci/intel8x0.c:596: codec_semaphore: semaphore is not ready
[0x1][0x700300]
ALSA sound/pci/intel8x0.c:611: codec_write 0: semaphore is not ready for
register 0x2c
That's the only thing. Sound works fine - it's only the message I'm
concernd about...
======================================================================
----------------------------------------------------------------------
nshmyrev - 01-13-05 23:35
----------------------------------------------------------------------
Still have the same problems with kernel 2.6.10 when I load snd_intel8x0
and snd_intel8x0m. For me that message doesn't brake anything, but it's
still not so pleasure to see warnings in syslog.
codec_semaphore: semaphore is not ready [0x1][0x701300]
codec_write 1: semaphore is not ready for register 0x54
Moreower, David Gómez <dabisu@gmail.com> reported that such messages
brakes sound working:
It's broken, at least in 2.6.10. In my case, if i loaded the modem
driver, the sound one stopped working (with a lot of semaphore
errors...) My solution is not using the modem driver by now :(. I
think that Takashi said that there was a problem in common
initialization in both drivers, so i hope it gets fixed soon ;)
So, hope this problem will be fixed somehow ;)
----------------------------------------------------------------------
phil - 11-24-05 10:06
----------------------------------------------------------------------
At the moment I'm using a Debian 2.6.14 kernel and Alsa 1.0.9b - and the
messages are gone.
Issue History
Date Modified Username Field Change
======================================================================
05-27-04 15:00 phil New Issue
05-27-04 15:00 phil Distribution => Debian sid
05-27-04 15:00 phil Kernel Version => vanilla 2.6.5
05-28-04 17:03 tiwai Note Added: 0001266
06-21-04 10:15 phil Note Added: 0001326
06-30-04 16:35 tiwai Note Added: 0001357
01-13-05 23:35 nshmyrev Note Added: 0003205
01-13-05 23:39 nshmyrev Issue Monitored: nshmyrev
11-24-05 10:06 phil Note Added: 0006839
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-11-24 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 9:06 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-14 19:00 [ALSA - driver 0000311]: error messages: boot process, application start bugtrack
2005-01-13 22:35 bugtrack
2004-06-30 14:35 noreply
2004-06-21 8:15 noreply
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=1e5773a358af10cbb0c92d37c3cd0965@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.