From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Which project to choose?
Date: Sat, 17 Jul 2010 08:22:03 +0800 [thread overview]
Message-ID: <AANLkTimdUFPBADtoDhiEjZPZSj8TkoAq_tPTJqDbWD2k@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1007160733020.4208@eeebox2.perex-int.cz>
2010/7/16 Jaroslav Kysela <perex@perex.cz>
> On Thu, 15 Jul 2010, Chris wrote:
>
> > On Thu, 2010-07-15 at 16:07 +0200, Jaroslav Kysela wrote:
> >> On Thu, 15 Jul 2010, Colin Guthrie wrote:
> >>
> >>> '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....
> >>
> >> Please, provide also /var/log/messages output for xrun_debug=11 - see
> >> http://www.alsa-project.org/main/index.php/XRUN_Debug for more details.
> We
> >> can detect the ALSA ring buffer issues in this way, too.
> >>
> >> Jaroslav
> >>
> > See pastebin file http://pastebin.com/MdENbSNd
> > Hopefully I did this correctly.
>
> Thanks. The hardware ring buffer pointers looks OK so it does not appear
> like a problem in our ALSA code. I would really consult these problems
> with PulseAudio developers. Return back, if they say that it's really
> ALSA issue, not the system scheduler issue.
>
> Note that for your configuration, you have the ring buffer containing only
> 0.1 second (it means that standard underruns can happen more frequently
> - usuall symptom is for example moving a window in X GUI).
>
> Jaroslav
>
>
Refer to the log , the values of pos and hwptr seem multiple of 8
5.5 PCI Data transfer
Only brust read/write transfers are allowed. All data transfer are 8 Long
Word brust transfers
This mean that the driver may need to limit the period bytes to be multiple
of 8 Long Word since interrupt occur when a cache fill/transfer between the
PCI memory and the internal memory.
snd_pcm_hw_constraint_step(runtime, 0, SNDRV_PCM_HW_PARAM_PERIOD_BYTES, 32);
and you may also need to set "rewind_safeguard" in PA too.
http://git.0pointer.de/?p=pulseaudio.git;a=commit;h=4df443bbe682055a41e7c2248877dcc7682a69b8
next prev parent reply other threads:[~2010-07-17 0:22 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 23:02 Which project to choose? Chris
2010-07-13 23:26 ` Raymond Yau
2010-07-14 0:01 ` Chris
2010-07-14 1:20 ` Raymond Yau
2010-07-14 1:31 ` Chris
[not found] ` <AANLkTimNSRELBq7i1Ypi9K2tmFu9NKLvQAOOqPwuU13x@mail.gmail.com>
[not found] ` <1279074303.29042.3.camel@localhost.localdomain>
2010-07-14 12:23 ` Raymond Yau
2010-07-14 22:15 ` Chris
2010-07-15 0:08 ` Raymond Yau
2010-07-15 1:38 ` Chris
2010-07-15 12:58 ` Colin Guthrie
2010-07-15 14:07 ` Jaroslav Kysela
2010-07-15 22:54 ` Chris
2010-07-15 23:15 ` Raymond Yau
2010-07-16 0:24 ` Chris
2010-07-16 5:32 ` Jaroslav Kysela
2010-07-16 1:19 ` Chris
2010-07-16 5:40 ` Jaroslav Kysela
2010-07-17 0:22 ` Raymond Yau [this message]
2010-07-15 22:02 ` Raymond Yau
2010-07-19 1:44 ` Raymond Yau
2010-07-19 2:56 ` Chris
2010-07-19 6:35 ` Raymond Yau
2010-07-19 7:53 ` Colin Guthrie
2010-07-19 22:52 ` Chris
2010-07-20 1:23 ` Raymond Yau
2010-07-20 2:13 ` Chris
2010-07-20 11:41 ` Raymond Yau
2010-07-20 22:19 ` Chris
2010-07-21 8:17 ` Raymond Yau
2010-07-21 22:57 ` Chris
2010-07-22 0:33 ` Raymond Yau
2010-07-22 1:07 ` Chris
[not found] ` <AANLkTim7iY_w96CPkVIlyB7Z9NGWUIvX2wKwvgu4wdjn@mail.gmail.com>
[not found] ` <1279766127.7841.11.camel@localhost.localdomain>
[not found] ` <AANLkTim_FkOXlYihEQikJ8Vpo5zXreCdqQnDW3acsrAu@mail.gmail.com>
[not found] ` <1279797682.7841.15.camel@localhost.localdomain>
2010-07-22 11:42 ` Raymond Yau
2010-07-20 22:49 ` Chris
2010-07-24 3:51 ` Raymond Yau
2010-07-25 14:14 ` Colin Guthrie
2010-07-26 5:53 ` Raymond Yau
2010-07-26 8:09 ` Raymond Yau
2010-07-15 13:08 ` Raymond Yau
2010-07-14 22:32 ` Raymond Yau
2010-07-14 22:58 ` Chris
2010-07-14 11:13 ` Raymond Yau
2010-07-14 15:06 ` David Henningsson
2010-07-14 15:25 ` Jaroslav Kysela
2010-07-14 19:45 ` David Henningsson
2010-07-14 22:13 ` Jaroslav Kysela
2010-07-16 0:39 ` Raymond Yau
2010-07-16 1:30 ` Raymond Yau
2010-07-15 0:52 ` Raymond Yau
2010-07-23 11:51 ` Raymond Yau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimdUFPBADtoDhiEjZPZSj8TkoAq_tPTJqDbWD2k@mail.gmail.com \
--to=superquad.vortex2@gmail.com \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).