From owner-cvs-all Tue Dec 1 00:00:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28321 for cvs-all-outgoing; Tue, 1 Dec 1998 00:00:36 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28310; Tue, 1 Dec 1998 00:00:31 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id IAA15189; Tue, 1 Dec 1998 08:58:51 +0100 (CET) To: Mike Smith cc: Peter Wemm , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_clock.c In-reply-to: Your message of "Mon, 30 Nov 1998 15:12:05 PST." <199811302312.PAA06127@dingo.cdrom.com> Date: Tue, 01 Dec 1998 08:58:51 +0100 Message-ID: <15187.912499131@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk >> Because I want the system to be bloddy unstable, weird and generally >> misbehaving, so that people actively have to acknowledge that it >> is broken in some way (hw and/or sw). > >This is totally screwed. Are you familiar with the expression "fail >safe"? We should *default* to the less efficient but functional >method, and make the unreliable method _optional_. Mike, I am not going to paste over this problem, it should be solved so that interrupt delivery on these systems works, not by pasting over the fact that they don't. Think about it, everything in the bloddy system will suffer under this bogosity, serial ports ? sorry but you're toast. Protocol timeouts ? well, eventually. real-time responses ? HA! We fully agree that we need to figure out the problem, absolutely, but if I paste over it in the timecounters, we will never hear about these systems, until something else is even more hosed. We found out why it happens on Wolfgangs system (lpip) and Bill Paul was a hosed X11 server/graphics card combination I think. I don't recall that we have even heard a response from you yet with some diagnostics in it, have we ? You may think that your laptop is perfectly all right, just because you have no other indication of failure, but I tell you: something is broken, and we should try to find it, rather than paste over the problem. If you'd rather paste, you know where the sysctl is, but then you have no case for whining like you do. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message