From owner-freebsd-current Tue Jan 30 08:42:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA05253 for current-outgoing; Tue, 30 Jan 1996 08:42:05 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA05237 for ; Tue, 30 Jan 1996 08:41:57 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0thIqD-00085AC; Tue, 30 Jan 96 10:23 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0thIlW-000CvTC; Tue, 30 Jan 96 10:18 WET Message-Id: Date: Tue, 30 Jan 96 10:18 WET To: freebsd-current@freebsd.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Tue Jan 30 1996, 10:18:41 CST Subject: Re: any ideas about this crash? Sender: owner-current@freebsd.org Precedence: bulk [5] Worse than that, it is fundamentally broken on machines that have [5]variable clocks (read: laptops and "green" PCs). The folks in Intel's [5]P6 architecture group were shocked when they heard about what we were [5]doing with the internal cycle counter..."It was never intended to be used [5]that way!". [5] At the very least, we should make it a compile-time option (defaulting [5]to off!). [5] -DG THANK YOU for saying that! I have been saying this for three months now and was ignored even though I was probably arguing the same points and looking at the same material out of Intels Oregon shop and from the chipset vendors that you were. This Pentium internal timer is USELESS as a TOD timepiece! Stop using it this way! It is only good for relative measurements within the processors realm. Why give the Linux guys something else to razz us about? Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" ^------(this is the fastest route)|"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983