2010/7/15 Colin Guthrie gmane@colin.guthr.ie
'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.
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....
it depend on whether PA developer willing to provide system time between
I/O operations of PA server
However , he can still use a small buffer size to force the PA server into underrun and we can know how PA server handle this situtation
aplay -D pulse --buffer-size=128 any.wav