Re: problems with playback via pcm device

2001-02-09 Thread Mike Holling
> > This could be related to the entropy gathering by the random kthread. Have you > > tried removing the random device from your kernel? > > yes, i've tried. no effect. This seems to have fixed the problem for me, thanks! I'm using the machine now and am getting no keyboard-related glitches in

Re: problems with playback via pcm device

2001-02-09 Thread Ilya Naumov
On Fri, 9 Feb 2001, John Baldwin wrote: > >> i have Ensoniq ES1371-based soundcard supported by pcm driver and > >> experience some problems. the sound played is interruped by clicks and > >> distorsions, and they appear more often when the disk activity is high. > >> during playback the kernel g

Re: problems with playback via pcm device

2001-02-09 Thread John Baldwin
On 09-Feb-01 Mike Holling wrote: >> i have Ensoniq ES1371-based soundcard supported by pcm driver and >> experience some problems. the sound played is interruped by clicks and >> distorsions, and they appear more often when the disk activity is high. >> during playback the kernel generates messag

Re: problems with playback via pcm device

2001-02-09 Thread Mike Holling
> i have Ensoniq ES1371-based soundcard supported by pcm driver and > experience some problems. the sound played is interruped by clicks and > distorsions, and they appear more often when the disk activity is high. > during playback the kernel generates messages like 'pcm0: hwptr went > backwards

Re: problems with playback via pcm device

2001-02-08 Thread Warner Losh
In message <[EMAIL PROTECTED]> Ilya Naumov writes: : during playback the kernel generates messages like 'pcm0: hwptr went : backwards 64 -> 32'. any ideas? : FreeBSD 5.0-CURRENT #2: Thu Feb 8 18:19:26 MSK 2001 Interrupt latency in current really sucks right now. Warner To Unsubscribe: send ma

problems with playback via pcm device

2001-02-08 Thread Ilya Naumov
i have Ensoniq ES1371-based soundcard supported by pcm driver and experience some problems. the sound played is interruped by clicks and distorsions, and they appear more often when the disk activity is high. during playback the kernel generates messages like 'pcm0: hwptr went backwards 64 -> 32'