From: Takashi Iwai <tiwai@suse.de>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: multi-channel playback regression
Date: Thu, 23 Jul 2009 10:36:36 +0200 [thread overview]
Message-ID: <s5hbpnbx0bv.wl%tiwai@suse.de> (raw)
In-Reply-To: <20090723083308.GA32173@localhost>
At Thu, 23 Jul 2009 16:33:08 +0800,
Wu Fengguang wrote:
>
> On Thu, Jul 23, 2009 at 04:15:59PM +0800, Takashi Iwai wrote:
> > At Thu, 23 Jul 2009 15:56:20 +0800,
> > Wu Fengguang wrote:
> > >
> > > On Thu, Jul 23, 2009 at 03:30:54PM +0800, Takashi Iwai wrote:
> > > > At Thu, 23 Jul 2009 15:22:53 +0800,
> > > > Wu Fengguang wrote:
> > > > >
> > > > > On Thu, Jul 23, 2009 at 03:01:21PM +0800, Takashi Iwai wrote:
> > > > > > At Thu, 23 Jul 2009 14:53:45 +0800,
> > > > > > Wu Fengguang wrote:
> > > > > > >
> > > > > > > Hi Takashi,
> > > > > > >
> > > > > > > When doing multi-channel playback tests on IbexPeak, I found that the
> > > > > > > following patch makes the playback enter an infinite loop, repeatedly
> > > > > > > playing a range of ~0.5s audio content. (Seems that some buffer
> > > > > > > pointer can never advance.)
> > > > > >
> > > > > > Could you set 1 to /proc/asound/card0/pcm0p/xrun_debug and give the
> > > > > > messages? Also, please show /proc/.../pcm0p/sub0/hw_params, too.
> > > > > >
> > > > > > The change affects only the code path for the problematic hardware
> > > > > > that reports wrong DMA position. So, if this change regresses, it
> > > > > > means that the device has been already problematic from the
> > > > > > beginning...
> > > > >
> > > > > I caught some messages:
> > > >
> > > > Is this with the patched (as is on sound git tree) kernel?
> > >
> > > Yes, it's unmodified latest git tree.
> > >
> > > > What if changing from #if 1 to #if 0?
> > >
> > > This makes 8-channel playback work again.
> >
> > OK, then could you apply the patch below, and do
> > "echo 9 > /proc/../xrun_debug", then gather the messages with both
> > #if 1 and #if 0? This will record the each snd_pcm_period_elpased()
> > so beware that you may get flood of messages.
>
> OK, but for now this box is doing something else that cannot interrupted.
> So I'll try the patch some time later. Sorry.
Sure, no problem.
Meanwhile, I'm thinking applying the debug-print patch now.
Any objection?
Takashi
next prev parent reply other threads:[~2009-07-23 8:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 6:53 multi-channel playback regression Wu Fengguang
2009-07-23 7:01 ` Takashi Iwai
2009-07-23 7:08 ` Wu Fengguang
2009-07-23 7:22 ` Wu Fengguang
2009-07-23 7:30 ` Takashi Iwai
2009-07-23 7:56 ` Wu Fengguang
2009-07-23 8:14 ` Jaroslav Kysela
2009-07-23 8:21 ` Takashi Iwai
2009-07-23 8:39 ` Jaroslav Kysela
2009-07-23 11:29 ` Takashi Iwai
2009-07-23 11:30 ` Takashi Iwai
2009-07-23 11:31 ` Jaroslav Kysela
2009-07-23 8:15 ` Takashi Iwai
2009-07-23 8:33 ` Wu Fengguang
2009-07-23 8:36 ` Takashi Iwai [this message]
2009-07-23 8:37 ` Jaroslav Kysela
2009-07-23 11:31 ` Takashi Iwai
2009-07-24 5:29 ` Wu Fengguang
2009-07-23 14:30 ` Takashi Iwai
2009-07-23 14:36 ` Jaroslav Kysela
2009-07-23 14:42 ` Takashi Iwai
2009-07-24 5:32 ` Wu Fengguang
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=s5hbpnbx0bv.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@intel.com \
/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