Bug 475236
| Summary: | snd-ens1371: snd_pcm_delay()/snd_pcm_avail() overflows | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter F. Patel-Schneider <pfpschneider> | ||||||
| Component: | kernel | Assignee: | Jaroslav Kysela <jkysela> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 10 | CC: | belegdol, bugs.michael, james, jbastian, johnthehammer23, kernel-maint, lkundrak, lpoetter, pachoramos1, yaneti | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-12-18 07:12:33 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 473302 | ||||||||
| Attachments: |
|
||||||||
|
Description
Peter F. Patel-Schneider
2008-12-08 16:35:23 UTC
Your sound driver is broken. It's an ALSA bug. The audio fd signals "writability", but snd_pcm_update_avail() says there's actually nothinbg to write. Hmm, so what should be done to notify the appropriate people then? I see a lot of these in the syslog, too, but I've not noticed sound breaking. This is with Intel HDA/Realtek 883 hardware: kernel-2.6.27.9-163.fc10.x86_64 pulseaudio-0.9.13-6.fc10.x86_64 alsa-lib-1.0.18-6.rc3.fc10.x86_64 alsa-lib-1.0.18-6.rc3.fc10.i386 [Tracking notice: I've filed Bug 478394 for this showing up on Intel HDA.] See bug 471941, comment 8 for a workaround for your message log filling up. *** Bug 473153 has been marked as a duplicate of this bug. *** FWIW, I'm still seeing this with Fedora 11 Beta/Rawhide. kernel-PAE-2.6.29.1-111.fc11.i686 pulseaudio-0.9.15-11.fc11.i586 I'm seeing a few similar messages too, e.g., "...nothing to read!" and some "exceptionally large value" errors. Apr 29 08:48:32 mollusk pulseaudio[2265]: alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 327153508 bytes (1854611 ms). Apr 29 08:48:32 mollusk pulseaudio[2265]: alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large: -326959556 bytes (-1853512 ms). Apr 29 08:48:36 mollusk pulseaudio[2265]: alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read! Apr 29 08:48:36 mollusk pulseaudio[2265]: alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_ens1371'. Please report thisissue to the ALSA developers. Apr 29 08:48:36 mollusk pulseaudio[2265]: alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. Apr 29 08:48:36 mollusk pulseaudio[2265]: alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Apr 29 08:48:36 mollusk pulseaudio[2265]: alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_ens1371'. Please report this issue to the ALSA developers. Apr 29 08:48:36 mollusk pulseaudio[2265]: alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. I'm now running 2.6.29.3-140.fc11.i586, and haven't seen the "nothing to read" bug showing up in several days of continuous sound play (obviously not all on this kernel). I have seen the following twice today, however: May 14 09:17:41 getafix pulseaudio[1890]: alsa-source.c: Increasing wakeup watermark to 35.99 ms May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 2147418208 bytes (24347145 ms). May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_ens1370'. Please report this issue to the ALSA developers. May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: snd_pcm_dump(): May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: Hardware PCM card 0 'Ensoniq AudioPCI' device 0 subdevice 0 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: Its setup is: May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: stream : CAPTURE May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: access : MMAP_INTERLEAVED May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: format : S16_LE May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: subformat : STD May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: channels : 1 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: rate : 44100 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: exact rate : 44100 (1411200/32) May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: msbits : 16 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: buffer_size : 32768 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: period_size : 32768 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: period_time : 743038 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: tstamp_mode : ENABLE May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: period_step : 1 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: avail_min : 32768 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: period_event : 0 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: start_threshold : -1 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: stop_threshold : 1073741824 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: silence_threshold: 0 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: silence_size : 0 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: boundary : 1073741824 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: appl_ptr : 819184 May 14 09:17:51 getafix pulseaudio[1890]: alsa-util.c: hw_ptr : 786464 May 14 09:17:51 getafix pulseaudio[1890]: alsa-source.c: Increasing minimal latency to 56.00 ms This is especially happening with kvm guests, since ens1370 is what is being emulated. *** Bug 497392 has been marked as a duplicate of this bug. *** I haven't seen this problem since alsa-lib 1.0.20 was installed, so it may have been eradicated. I reported bug 497392 and my sound card isn't Ensoniq ES1370 , its a HDA with realtek chip. Either this bug isn't named properly or my bug was erroneously marked as duplicate. I can still reproduce the problem with kvm guest: Fedora 11 i386 guest Fedora 10 x86_64 host alsa-lib-1.0.20-1.fc11.i586 alsa-plugins-pulseaudio-1.0.18-3.fc11.i586 alsa-utils-1.0.20-3.fc11.i586 Please keep in mind that i586 kernel has to be running, i686 pae won't work at all due to bug #492838. Created attachment 344593 [details]
Log of pulseaudio -vvvv running rhythmbox for a while
The only thing that goes out of the speakers is a looping first few miliseconds of the song. In case that matters, this is with kernel 2.6.29.3-140.fc11.i586 running on the guest.
What is written in comment 7 also affects me with Fedora 11. Created attachment 349107 [details]
kernel messages on snd_hda_intel
I'm seeing similar on snd_hda_intel.
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
Subsystem: ASUSTeK Computer Inc. Device 834a
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f7eb8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
kernel-2.6.29.4-167.fc11.i586
pulseaudio-0.9.15-11.fc11.i586
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |