From: "D. Sen" <dsen@homemail.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: intel8x0: changing characteristics after an APM suspend-resume cycle
Date: Wed, 08 Jan 2003 09:25:19 -0500 [thread overview]
Message-ID: <3E1C34CF.10903@homemail.com> (raw)
In-Reply-To: s5h7kdfalxd.wl@alsa2.suse.de
Takashi Iwai wrote:
> At Tue, 07 Jan 2003 15:40:10 -0500,
> D. Sen <dsen@homemail.com> wrote:
>
>>Hi,
>>
>>I am using the snd-intel8x0 drivers (0.9.0rc6) on my IBM Thinkpad
>>running Linux 2.4.20. Everything seems to run fine until the machine
>>goes through a suspend/resume cycle when mono files/streams seem to get
>>played back at a much faster rate.
>>
>>A cold reboot resolves the problem.
>
>
> even after unloading/reloading the module the problem persists?
>
>
> Takashi
>
>
While unloading/reloading does resolve the problem, once in a while
though, sound is totally stuffed up after the
suspend/resume cycle and the modules cant be reloaded. Typically happens
if I forget to unmute the
channels after resume and attempt to play something. At that point
trying to reload the modules is not possible (see the messages below). A
suspend/resume cycle resolves the problem.
[/root] modprobe -a snd-intel8x0
/lib/modules/2.4.20/kernel/sound/pci/snd-intel8x0.o: init_module: No
such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
modprobe: insmod /lib/modules/2.4.20/kernel/sound/pci/snd-intel8x0.o failed
modprobe: insmod snd-intel8x0 failed
and in the syslog:
Jan 8 08:33:32 localhost kernel: PCI: Found IRQ 11 for device 00:1f.5
Jan 8 08:33:32 localhost kernel: PCI: Sharing IRQ 11 with 00:1f.3
Jan 8 08:33:32 localhost kernel: PCI: Sharing IRQ 11 with 00:1f.6
Jan 8 08:33:32 localhost kernel: PCI: Sharing IRQ 11 with 02:00.1
Jan 8 08:33:33 localhost kernel: ALSA
../../alsa-kernel/pci/ac97/ac97_codec.c:1554: AC'97 0:0 does not respond
- RESET [REC_GAIN = 0x0]
Jan 8 08:33:33 localhost kernel: Intel ICH soundcard not found or
device busy
Jan 8 03:40:47 localhost kernel: PCI: Found IRQ 11 for device 00:1f.5
Jan 8 03:40:47 localhost kernel: PCI: Sharing IRQ 11 with 00:1f.3
Jan 8 03:40:47 localhost kernel: PCI: Sharing IRQ 11 with 00:1f.6
Jan 8 03:40:47 localhost kernel: PCI: Sharing IRQ 11 with 02:00.1
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x26
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x0
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x26
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x20
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x26
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x2
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:546: codec_read 0: semaphore is not ready
for register 0x2
Jan 8 03:40:47 localhost last message repeated 9 times
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x2
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x4
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x6
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0xa
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0xc
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0xe
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x10
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x12
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x14
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x16
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x18
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x1a
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x1c
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x20
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x22
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x2a
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x2c
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x32
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x70
Jan 8 03:40:47 localhost kernel: ALSA
../alsa-kernel/pci/intel8x0.c:530: codec_write 0: semaphore is not ready
for register 0x74
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
prev parent reply other threads:[~2003-01-08 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 20:40 intel8x0: changing characteristics after an APM suspend-resume cycle D. Sen
2003-01-08 12:03 ` Takashi Iwai
2003-01-08 13:46 ` D. Sen
2003-01-08 16:38 ` Takashi Iwai
2003-02-09 5:38 ` D. Sen
[not found] ` <3E4B0622.8070500@homemail.com>
2003-02-14 11:35 ` Takashi Iwai
2003-01-08 14:25 ` D. Sen [this message]
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=3E1C34CF.10903@homemail.com \
--to=dsen@homemail.com \
--cc=alsa-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox