On Mon, 2010-07-19 at 09:44 +0800, Raymond Yau wrote: > 2010/7/15 Colin Guthrie <gmane@xxxxxxxxxxxxxx> > > > 'Twas brillig, and Chris at 15/07/10 02:38 did gyre and gimble: > > > On Thu, 2010-07-15 at 08:08 +0800, Raymond Yau wrote: > > > > > >>> I posted both of those bug reports. Honestly, I just want it to work > > >>> without all the error output to syslog and thrashing of my HD for > > >>> minutes at a time. As I said, I've got the output of pulseaudio -vvvvv > > >>> if anyone would like to look at it and tell me what I need to do to fix > > >>> the problem. > > >>> > > >>> Chris > > >>> > > >>> > > >>> > > >> Just upload your current pulseaudio.log and output of alsa-info.sh to > > >> mandriva 's bugzilla > > >> > > >> Cannot obtain any conclusion based on the log which you have posted last > > >> year ( xmms) > > >> > > >> as Jaroslav Kysela said , need the real system time between I/O > > operations > > >> and you'll see if it's issue in the ALSA driver or a task scheduling > > >> problem. > > > > > > Here is the bug report with the outputs uploaded. > > > > > > https://qa.mandriva.com/show_bug.cgi?id=60169 > > > > Well seeing as my process when getting such a bug is to report it here > > on behalf of the user, I suspect that this has reached a stalemate.... > > > > > > > Refer to https://qa.mandriva.com/show_bug.cgi?id=56473#c10 > > I have installed mandriva 2010 on virtual box > > when using xmms and libao output plugin to play system sound startup3.wav > > xmms hang at the end of the playback only when enable buffering in libao > output plugin.(configure output plugin in xmms, unfortunately default is > enable buffering buffer size 3000 chunk size 1000) , > > xmms does not hang when you disable the buffer or using liboss/libALSA > output plugin > > The last message in the pulseaudio server is > D: protocol-native.c 'underrun on libao[xmms] playback stream' , 0 bytes in > queue. > > The sound card seem running since hw_ptr and appl_ptr are increasing when > cat /proc/asound/card0/pcm0p/sub0/status > > After a while , the following message appear > > E:alsa-sink.c : ALSA woke us up to write new data , but there was actually > nothing to write! The above is exactly what I see periodically Raymond, so, what, if any, is the fix? Chris -- Chris KeyID 0xE372A7DA98E6705C
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
