From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000311]: error messages: boot process, application start
Date: Wed, 30 Jun 2004 16:35:45 +0200 [thread overview]
Message-ID: <80d6afeefd36037fc9e0bcb568af0e1a@bugtrack.alsa-project.org> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000311
======================================================================
Reported By: phil
Assigned To:
======================================================================
Project: ALSA - driver
Bug 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: 06-30-2004 16:35 CEST
======================================================================
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...
======================================================================
----------------------------------------------------------------------
tiwai - 05-28-2004 17:03 CEST
----------------------------------------------------------------------
could you try 1.0.5? at least this kind of messages should appear
only once in this version.
----------------------------------------------------------------------
phil - 06-21-2004 10:15 CEST
----------------------------------------------------------------------
I tried 1.0.5a-1 (debian package) and got still the same message with the
same quantity.
----------------------------------------------------------------------
tiwai - 06-30-2004 16:35 CEST
----------------------------------------------------------------------
Well, these messages are harmless, so you can ignore safely.
I'll disable the first message ("no device found" from seq_oss_init.c).
The messages about codec appear when the driver probes the secondary
codec, which is likely a modem codec.
Bug History
Date Modified Username Field Change
======================================================================
05-27-04 15:00 phil New Bug
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 Bugnote Added: 0001266
06-21-04 10:15 phil Bugnote Added: 0001326
06-30-04 16:35 tiwai Bugnote Added: 0001357
======================================================================
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next reply other threads:[~2004-06-30 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 14:35 noreply [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-11-24 9:06 bugtrack
2005-01-13 22:35 bugtrack
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=80d6afeefd36037fc9e0bcb568af0e1a@bugtrack.alsa-project.org \
--to=noreply@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.