Re: bogus microuptime() warnings?

2001-01-11 Thread Warner Losh
In message [EMAIL PROTECTED] John Baldwin writes: : Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" : with the latest -CURRENT than I used to... : : Which soundcard? I get them on sbc0: ESS ES1879 at port 0x220-0x22f,0x388-0x38b,0x320-0x321 irq 5 drq 1,5 on isa0 pcm0:

Re: bogus microuptime() warnings?

2001-01-11 Thread Nate Dannenberg
On Thu, 11 Jan 2001, Warner Losh wrote: In message [EMAIL PROTECTED] John Baldwin writes: : Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" : with the latest -CURRENT than I used to... : : Which soundcard? sbc0: ESS ES1879 at port

Re: bogus microuptime() warnings?

2001-01-10 Thread Dag-Erling Smorgrav
John Baldwin [EMAIL PROTECTED] writes: On 09-Jan-01 Dag-Erling Smorgrav wrote: Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" with the latest -CURRENT than I used to... Which soundcard? SoundBlaster Vibra 16X. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To

Re: bogus microuptime() warnings?

2001-01-09 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes: I regularly get "microuptime() went backwards" warnings on my desktop box. The funny thing about them is that the reported timevals have the same seconds part, but the microseconds part of the second timeval is so large that it's wrapped

Re: bogus microuptime() warnings?

2001-01-09 Thread Dag-Erling Smorgrav
Poul-Henning Kamp [EMAIL PROTECTED] writes: No, this is either a problem reading the i8254 timecounter reliably or an interrupt latency problem. Given that this is -CURRENT, interrupt latency is a likely explanation... Going off on a tangent, I'm getting a lot fewer "hwptr went backwards"

Re: bogus microuptime() warnings?

2001-01-09 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes: Poul-Henning Kamp [EMAIL PROTECTED] writes: No, this is either a problem reading the i8254 timecounter reliably or an interrupt latency problem. Given that this is -CURRENT, interrupt latency is a likely explanation... Going off on a

Re: bogus microuptime() warnings?

2001-01-09 Thread John Baldwin
On 09-Jan-01 Dag-Erling Smorgrav wrote: Poul-Henning Kamp [EMAIL PROTECTED] writes: No, this is either a problem reading the i8254 timecounter reliably or an interrupt latency problem. Given that this is -CURRENT, interrupt latency is a likely explanation... Going off on a tangent, I'm

Re: bogus microuptime() warnings?

2001-01-09 Thread Szilveszter Adam
On Tue, Jan 09, 2001 at 04:11:16PM -0800, John Baldwin wrote: Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" with the latest -CURRENT than I used to... Which soundcard? SB 64 AWE ISA PNP... almost no hwptr... messages any more and sound is no longer popping under