[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Jackd Problems -- alsa_pcm: xrun of at least 1227061150613.504 msecs

On Wed, 2008-11-19 at 18:49 -0200, Paulo Cavalcanti wrote:

> On Wed, Nov 19, 2008 at 1:28 AM, Jonathan Ryshpan <jonrysh pacbell net> wrote:
>         In the past I've never had any problems running jackd.  Now I'm getting
>         a very large number of messages reading:
>                **** alsa_pcm: xrun of at least 1227061150613.504 msecs
>         I'm running F9 on an x86_64 system with all updates installed.
>         Pulseaudio is not running.  Jackd is started via qjackctl.  No past
>         problems with audio beyond the usual conflicts between pulseaudio and
>         firefox.
>         Questions:
>         (1) What exactly does this message mean?  An "xrun" is a buffer under-
>         or over-run -- but what does the time interval represent?
>         (2) Whatever the time interval means, it looks rather large.
>         1227061150613.504 msec is many days (or maybe years if msec means
>         millisec and not microsec)  This looks like a misconfiguration of some
>         kind or a missing component.  Any idea what it might be?
> The solution depends on your card (I have an Intel onboard card). 
> But this material may give you an idea on what you can try:
>  http://people.atrpms.net/~pcavalcanti/alsa-1.0.15rc2_snd-hda-intel.html#jack

Thanks for the very useful pointer.  Now I am stuck on what ought to be
a very simple problem:  What "option"s can be given to my own driver (or
generally any alsa driver)?  My own driver appears to be snd_intel8x0,
which is documented at
Unfortunately the "parm:"s (supposing these the possible arguments to an
"option" statement in modules.conf) don't seem to include all possible
options to be applied to this module.

Sorry for being so dense - jon


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]