Error at playback that occurs is: Fehler Audio: Mär 03 21:04:38 erde kernel: ca0106: unstable DMA pointer! Mär 03 21:04:38 erde pulseaudio[9893]: [pulseaudio] main.c: User-configured server at {871781b4d90447dda660c1fe49aa13fc}unix:/run/user/500/ pulse/native, which appears to be local. Probing deeper. Mär 03 21:04:38 erde rtkit-daemon[1386]: Successfully made thread 9896 of process 9896 (/usr/bin/pulseaudio) owned by '500' high priority a t nice level -11. Mär 03 21:04:38 erde rtkit-daemon[1386]: Supervising 1 threads of 1 processes of 1 users. Mär 03 21:04:38 erde pulseaudio[9896]: [pulseaudio] pid.c: Stale PID file, overwriting. Mär 03 21:04:38 erde pulseaudio[9896]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Mär 03 21:04:38 erde rtkit-daemon[1386]: Supervising 1 threads of 1 processes of 1 users. Mär 03 21:04:38 erde rtkit-daemon[1386]: Successfully made thread 9897 of process 9896 (/usr/bin/pulseaudio) owned by '500' RT at priority 5. Mär 03 21:04:38 erde rtkit-daemon[1386]: Supervising 2 threads of 1 processes of 1 users. Mär 03 21:04:38 erde pulseaudio[9896]: [pulseaudio] source.c: Default and alternate sample rates are the same. Mär 03 21:04:38 erde rtkit-daemon[1386]: Supervising 2 threads of 1 processes of 1 users. Mär 03 21:04:38 erde rtkit-daemon[1386]: Successfully made thread 9898 of process 9896 (/usr/bin/pulseaudio) owned by '500' RT at priority 5. Mär 03 21:04:38 erde rtkit-daemon[1386]: Supervising 3 threads of 1 processes of 1 users. Mär 03 21:04:39 erde pulseaudio[9896]: [alsa-sink-ca0106] alsa-sink.c: ALSA weckte uns auf, um neue Daten auf das Gerät zu schreiben, doch es gab nichts zum Schreiben! Mär 03 21:04:39 erde pulseaudio[9896]: [alsa-sink-ca0106] alsa-sink.c: Dies ist höchstwahrscheinlich ein Fehler im ALSA-Treiber 'snd_ca0106 '. Bitte melden Sie diesen Fehler den ALSA-Entwicklern. Mär 03 21:04:39 erde pulseaudio[9896]: [alsa-sink-ca0106] alsa-sink.c: Wir wurden durch das POLLOUT-Set geweckt, allerdings lieferte ein an schliessender snd_pcm_avail() den Wert 0 oder einen anderen Wert < min_avail. Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedAssignee: bugsquad => tmb
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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 Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD