Re: bogus microuptime() warnings?
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: ESS 18xx DSP on sbc0 on m VAIO. I see them more when there's lots of traffic on my zoomair awi card. But I also see them when playing mp3s off my hard disk. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
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 0x220-0x22f,0x388-0x38b,0x320-0x321 irq 5 drq 1,5 on isa0
pcm0: ESS 18xx DSP on sbc0
I have also been experiencing this problem ("hwptr went backwards") with
my ESS Audiodrive (integrated on the motherboard), which uses the same
chip of course. Also, mine shows up as pcm1, rather than pcm0 as it did
in 4.1-Release, and I am forced to use a bridge driver. What am I doing
wrong?
Do you get stereo playback from yours? Mine's only mono in anything
over 4.1-Release. Of course I'm tracking 5.0-current.
But I also see them when playing mp3s off my hard disk.
Ditto.
--
___ _ _
| _///@@@| |
| [EMAIL PROTECTED] /'//ZZ@@| |
| |'''/|'/@7 |
| http://home.kscable.com/natedac |`'| `~~' |
| | `| .--. |
| C64/C128 - What's *YOUR* hobby? | `\|___\ |
| \_ | |
|___ \_| _|
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
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 Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
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 around to a negative number (causing the signed comparison to report that it went backwards). This suggests that the current process has been running uninterrupted for several seconds, which seems unlikely - or that the timecounter was adjusted upwards while the process was running (could ntp cause that?) No, this is either a problem reading the i8254 timecounter reliably or an interrupt latency problem. If you sysctl's indicate that you are running on the TSC timecounter and you can reproduce this there is some chance we can create a workaround. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
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" with the latest -CURRENT than I used to... If you sysctl's indicate that you are running on the TSC timecounter and you can reproduce this there is some chance we can create a workaround. I'll check. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
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 tangent, I'm getting a lot fewer "hwptr went backwards" with the latest -CURRENT than I used to... That's also the irq-latency if I understand it right. The latency went from "abysmal" to "bad" recently. We used to do "ok". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
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 getting a lot fewer "hwptr went backwards" with the latest -CURRENT than I used to... Which soundcard? -- 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: bogus microuptime() warnings?
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 normal circumstances. (even if eg disk io is in progress) I was already rejoicing about this to the list in the last millenium... ( 30th December to be precise:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
