intel8x0: changing characteristics after an APM suspend-resume cycle

intel8x0: changing characteristics after an APM suspend-resume cycle

[D. Sen]

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.

Any ideas on how I can solve this?

Thanks,
DS

lspci --vv output for the Audio Chipset:

00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio 
(rev 02)
	Subsystem: IBM: Unknown device 0508
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 11
	Region 0: I/O ports at 1c00 [size=256]
	Region 1: I/O ports at 18c0 [size=64]



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

Re: intel8x0: changing characteristics after an APM suspend-resume cycle

[Takashi Iwai]

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


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

Re: intel8x0: changing characteristics after an APM suspend-resume cycle

[D. Sen]

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
> 
> 

I just tried unloading/reloading the modules (had to close mixer 
applications, etc first). But you are right. The problem does NOT 
persist if I unload and then reload the modules.



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

Re: intel8x0: changing characteristics after an APM suspend-resume cycle

[D. Sen]

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

Re: intel8x0: changing characteristics after an APM suspend-resume cycle

[Takashi Iwai]

At Wed, 08 Jan 2003 08:46:19 -0500,
D. Sen <dsen@homemail.com> wrote:
> 
> 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
> > 
> > 
> 
> I just tried unloading/reloading the modules (had to close mixer 
> applications, etc first). But you are right. The problem does NOT 
> persist if I unload and then reload the modules.

hmm, then something lack in the resume procedure.
i guess the restoration of ac97 registers are not enough.
will take a look later.

thanks for your info!


ciao,

Takashi


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

Re: intel8x0: changing characteristics after an APM suspend-resume cycle

[D. Sen]

Just reporting that the RC7 release did not fix the problem I reported a 
while ago (that the driver doesnt "survive" a suspend/resume cycle on an 
IBM T-30)

Takashi Iwai wrote:
> At Wed, 08 Jan 2003 08:46:19 -0500,
> D. Sen <dsen@homemail.com> wrote:
> 
>>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
>>>
>>>
>>
>>I just tried unloading/reloading the modules (had to close mixer 
>>applications, etc first). But you are right. The problem does NOT 
>>persist if I unload and then reload the modules.
> 
> 
> hmm, then something lack in the resume procedure.
> i guess the restoration of ac97 registers are not enough.
> will take a look later.
> 
> thanks for your info!
> 
> 
> ciao,
> 
> Takashi
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 
> 

-- 
---------------------------------------
D. Sen, PhD
21 Woodmont Drive
Randolph
NJ 07869
Home Email: dsen@homemail.com   Tel: 973 216 2326
Work Email: dsen@ieee.org       Web: http://www.auditorymodels.org/~dsen



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

Re: intel8x0: changing characteristics after an APM suspend-resume cycle

[Takashi Iwai]

At Thu, 13 Feb 2003 13:42:42 +1100,
D. Sen <dsen@homemail.com> wrote:
> 
> Hi Takashi,
> 
> I am wondering if you had a chance to look at the 'resume' procedure. 
> Its really frustrating having to shutdown all the audio applications (I 
> have lots) and restarting them after the resume.

sorry, i haven't changed the code yet since i have no time left for
investigating this problem.

can you do the following small test?

- playback a 44100 (or 48000) hz file
- suspend/resume
- playback the same file again.
- if the playback is too fast, playback a file with different sample
  rate once.
- playback the file above again.


also, please get the dump of /proc/asound/card0/ac97#0regs
before and after suspend/resume (and after playback, too), and compare
whether the values are different.


thanks,

Takashi


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en