Date: Wed, 07 Feb 2001 17:02:51 -0700 From: Warner Losh <imp@harmony.village.org> To: farid.hajji@ob.kamp.net Cc: brian@Awfulhak.org, domi@saargate.de, freebsd-current@FreeBSD.ORG Subject: Re: Strange fopen() behaviour Message-ID: <200102080003.f1802p996815@harmony.village.org> In-Reply-To: Your message of "Wed, 07 Feb 2001 00:34:18 %2B0100." <200102062334.f16NYI229243@mail-ob.kamp.net> References: <200102062334.f16NYI229243@mail-ob.kamp.net> <200102060324.f163O0610286@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200102062334.f16NYI229243@mail-ob.kamp.net> Farid Hajji writes: : > dev.lan.Awfulhak.org kernel log messages: : > > microuptime() went backwards (18415.166882 -> 18415.158249) : > > microuptime() went backwards (18490.192910 -> 18490.187579) : > > microuptime() went backwards (19572.644000 -> 19572.638237) : > > microuptime() went backwards (19878.637972 -> 19878.637330) : > > microuptime() went backwards (20043.869158 -> 20043.868971) : > > microuptime() went backwards (20074.159108 -> 20074.152253) : > > microuptime() went backwards (20210.078270 -> 20210.072448) : I'm also seing this as of CURRENT-2001-01-27 and later: : pcm1: hwptr went backwards 36 -> 0 : pcm1: hwptr went backwards 40 -> 16 : pcm1: hwptr went backwards 2084 -> 2048 : pcm1: hwptr went backwards 2092 -> 2064 That's different. It is a sound thing that's related to the really crappy interrupt performance that we have in current. You'll likely see it as far back as october or so (I was seeing them at BSDCON). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102080003.f1802p996815>