All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: 2.6.30-rc8 skipping regression also affects cmipci
Date: Thu, 17 Dec 2009 10:46:03 +0800	[thread overview]
Message-ID: <4f3252890912161846nee2a6bfmf882a7d7b0200a5a@mail.gmail.com> (raw)
In-Reply-To: <hgbiph$4kr$1@ger.gmane.org>

2009/12/17 Frédéric Brière <fbriere@fbriere.net>

> Hi everybody,
>
> I was only recently able to upgrade from 2.6.26 to 2.6.32 (long story).
> In so doing, I noticed infrequent occurrences of audio skipping, which I
> managed to bisect down to c87d973.  It would appear that this commit
> also affects cmipci (CMI8738), albeit not as badly as it did for
> intel8x0.  (I guess I'm the only person left on Earth still using a
> stand-alone PCI sound card, which is why this was never reported.  <g>)
>


http://git.alsa-project.org/?p=alsa-kernel.git;a=commit;h=c87d9732004b3f8fd82d729f12ccfb96c0df279e

The patch seem just fix the problem of the usb audio card in

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4523


This patch actually cause pulseaudio 0.9.14 server abort on my au8830

E: memblock.c: Assertion 'length' failed at pulsecore/memblock.c:356,
function pa_memblock_new_fixed(). Aborting.

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4455#c20892

and the output by using 48000 x 256 Hz Clock in Vortex chip

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4455#c20905


That's why I still stay with the driver come with Fedora 10
2.6.27.41-170.2.117.fc10.i686

  reply	other threads:[~2009-12-17  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 21:17 2.6.30-rc8 skipping regression also affects cmipci Frédéric Brière
2009-12-17  2:46 ` Raymond Yau [this message]
2010-03-02  2:10 ` Frédéric Brière
2010-03-07  4:41   ` 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=4f3252890912161846nee2a6bfmf882a7d7b0200a5a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.