From owner-freebsd-current Sun Mar 18 19:48:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 61A0537B718; Sun, 18 Mar 2001 19:48:11 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id OAA18011; Mon, 19 Mar 2001 14:47:53 +1100 Date: Mon, 19 Mar 2001 14:47:34 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: David Malone Cc: Dag-Erling Smorgrav , current@FreeBSD.ORG, jhb@FreeBSD.ORG, jake@FreeBSD.ORG, Ian Dowse Subject: Re: Interesting backtrace... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Mar 2001, Bruce Evans wrote: > K6-2's aren't really i586's and i586_bzero should never be used for > them (generic bzero is faster), but there is apparently another > bug that may cause them to be used. From des's dmesg output: > > > i586_bzero() bandwidth = -1980152482 bytes/sec > ^ > > bzero() bandwidth = 129299198 bytes/sec > > i586_bzero gets used because negative bandwidths are significantly ^^^^^^^^^ oops, I meant "should not get used" > smaller than positive ones, so plain bzero is faster according to this > message, but whatever the overflow apparently causes other bad things. The overflow is actually only in the error message. It is caused by a preposterous value for `usec'. > npx.c already has one "fix" for the overflow problem. The problem > is may be that clocks don't work early any more. It must be that microtime() doesn't work early any more. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message