Re: pcm status
On 20-Jan-01 Donald J . Maddox wrote: > This is directly traceable to entropy harvesting by /dev/*random. > I know it's not an option if you need to use ssh, but not loading > random.ko will fix the sound problems when moving the mouse or > typing. It doesn't fix the 'hwptr went backwards' messages, though. The entropy stuff only kicks in on the keyboard and mouse. It can't really help the hwptr backwards stuff, as that is due to the additional overhead in the current interrupt path as well as asynchronous handling of interrupts. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm status
OK, please try this, then; change the HARVEST_RING_SIZE in sys/dev/random/yarrow.h to a smaller power-of-2 (256 or 128 would be good), and let me know how that helps-or-not. Thanks! M > If it helps at all, it's marginal. I still get skips. > > On Sat, Jan 20, 2001 at 05:36:08PM +0200, Mark Murray wrote: > > > This is directly traceable to entropy harvesting by /dev/*random. > > > I know it's not an option if you need to use ssh, but not loading > > > random.ko will fix the sound problems when moving the mouse or > > > typing. It doesn't fix the 'hwptr went backwards' messages, though. > > > > Please tell me if > > > > sysctl -w kern.random.yarrow.bins=2 > > makes a difference for you. > > > > Thanks! > > > > M > > -- > > Mark Murray > > Warning: this .sig is umop ap!sdn > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm status
If it helps at all, it's marginal. I still get skips. On Sat, Jan 20, 2001 at 05:36:08PM +0200, Mark Murray wrote: > > This is directly traceable to entropy harvesting by /dev/*random. > > I know it's not an option if you need to use ssh, but not loading > > random.ko will fix the sound problems when moving the mouse or > > typing. It doesn't fix the 'hwptr went backwards' messages, though. > > Please tell me if > > sysctl -w kern.random.yarrow.bins=2 > makes a difference for you. > > Thanks! > > M > -- > Mark Murray > Warning: this .sig is umop ap!sdn > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm status
> This is directly traceable to entropy harvesting by /dev/*random. > I know it's not an option if you need to use ssh, but not loading > random.ko will fix the sound problems when moving the mouse or > typing. It doesn't fix the 'hwptr went backwards' messages, though. Please tell me if sysctl -w kern.random.yarrow.bins=2 makes a difference for you. Thanks! M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm status
This is directly traceable to entropy harvesting by /dev/*random. I know it's not an option if you need to use ssh, but not loading random.ko will fix the sound problems when moving the mouse or typing. It doesn't fix the 'hwptr went backwards' messages, though. On Fri, Jan 19, 2001 at 11:42:32PM -0700, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Sean Kelly writes: > : I did not have this behavior in -STABLE, but now I do since I upgraded > : to -CURRENT. > > -current's interrupt latency is horrible these days, which seems to > manifest itself in problem with the sound driver. I have a -current > laptop and get all kinds of artifacts on it. I have a laptop that is > running -stable and has 1/3 the power of the -current laptop and plays > w/o a hitch. > > Warner > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm status
In message <[EMAIL PROTECTED]> Sean Kelly writes: : I did not have this behavior in -STABLE, but now I do since I upgraded : to -CURRENT. -current's interrupt latency is horrible these days, which seems to manifest itself in problem with the sound driver. I have a -current laptop and get all kinds of artifacts on it. I have a laptop that is running -stable and has 1/3 the power of the -current laptop and plays w/o a hitch. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
