> > If this is a known problem, I'll stop for now and watch out for fixes.
> > If it's not the expected behaviour from the PCM driver though, can
> > anyone advise?
> Okay, just checked and it appears tha htis is the same error that I'm
> seeing on mine, as reported yesterday ... not sure if its known or not,
> but its not "just you" ...

are either of you using esound or xmms?  if so, i know the cause of this and
it will be fixed shortly, once my primary development box recovers from
killing its cpu.

if not, i'll try to reproduce this.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to