From: Andoru <andoru.blah@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Invalid PCM pointer with CMI8738 and pcm.c buffer underuns
Date: Mon, 28 Apr 2014 21:28:42 +0000 (UTC) [thread overview]
Message-ID: <loom.20140428T232433-313@post.gmane.org> (raw)
[Continued from here:
http://thread.gmane.org/gmane.linux.alsa.devel/122028/focus=122354 ]
> It's way too old. Better to build the latest kernel.
The latest kernel available for my distro, or the latest kernel available
"from Linus"? I've already tried the former.
> You need to figure out the condition reproducing the issue.
For all I know (I'm not that knowledgeable on those things, mind you) this
happens completely at random. There hasn't been any pattern when the PC
would become unusable, and the OS unresponsive.
> For example, application may apply some strange buffer size and period
> size the hardware chip doesn't like. If so, changing the buffer size
> and/or period size may reduce the problem.
I'm not aware of any feature to change the buffer size in any of the
programs that cause the lock-ups.
> Meanwhile, you can try the patch below, too, which aligns the period
That patch is for kernel sources or for the above snapshots I mentioned? Or
perhaps there are more recent ALSA source codes?
next reply other threads:[~2014-04-28 21:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 21:28 Andoru [this message]
2014-04-29 6:04 ` Invalid PCM pointer with CMI8738 and pcm.c buffer underuns Takashi Iwai
2014-04-29 13:06 ` Andoru
2014-04-29 14:26 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2014-04-20 15:04 Andoru
2014-04-28 16:00 ` Takashi Iwai
2014-04-29 1:12 ` Andoru
2014-04-10 19:05 andoru
2014-04-12 4:38 ` Raymond Yau
2014-04-12 17:56 ` Andoru
2014-04-12 23:38 ` Andoru
2014-04-04 16:15 andoru
2014-04-05 6:21 ` Raymond Yau
2014-04-05 18:29 ` andoru
2014-04-05 21:55 ` Raymond Yau
2014-04-05 23:16 ` andoru
[not found] <CAAvHfitJ2B1sr7_6h=ww_SVGgsuy4iNLGc3CjDyiNtwdpJTSUw@mail.gmail.com>
2014-04-01 11:37 ` Clemens Ladisch
2014-04-01 18:48 ` andoru
2014-04-01 22:58 ` Raymond Yau
2014-04-02 2:24 ` andoru
2014-03-26 16:02 andoru
[not found] ` <CAN8ccib45znh-JbH57EhfbPNQg_fginmX9Tbr=yKMmd4D=iygQ@mail.gmail.com>
[not found] ` <CAN8cciZkGx5XBO+u0b7V9YN8VU_rz8ckL8B=6oBFJr+-Yg8cxw@mail.gmail.com>
2014-03-26 23:23 ` Raymond Yau
2014-03-27 20:44 ` andoru
2014-03-28 4:46 ` Raymond Yau
2014-03-28 8:42 ` Clemens Ladisch
2014-03-28 14:28 ` andoru
2014-03-28 15:21 ` Clemens Ladisch
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=loom.20140428T232433-313@post.gmane.org \
--to=andoru.blah@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.