From owner-freebsd-current Fri Aug 23 21:21:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB89B37B400 for ; Fri, 23 Aug 2002 21:21:20 -0700 (PDT) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1542543E3B for ; Fri, 23 Aug 2002 21:21:19 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.5/8.12.5) with ESMTP id g7O4LUJ7003729; Fri, 23 Aug 2002 21:21:30 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.5/8.12.5/Submit) id g7O4LSVB003728; Fri, 23 Aug 2002 21:21:28 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Fri, 23 Aug 2002 21:21:28 -0700 From: David Schultz To: Bosko Milekic Cc: Martin Blapp , Terry Lambert , Julian Elischer , Don Lewis , sos@freebsd.dk, marks@ripe.net, ktsin@acm.org, freebsd-current@FreeBSD.ORG Subject: Re: Memory corruption in CURRENT Message-ID: <20020824042128.GB3612@HAL9000.homeunix.com> Mail-Followup-To: Bosko Milekic , Martin Blapp , Terry Lambert , Julian Elischer , Don Lewis , sos@freebsd.dk, marks@ripe.net, ktsin@acm.org, freebsd-current@FreeBSD.ORG References: <3D663D71.C1DBD78E@mindspring.com> <20020823155725.T50084-100000@levais.imp.ch> <20020823095944.A38366@unixdaemons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020823095944.A38366@unixdaemons.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Bosko Milekic : > All Intel chips are fairly buggy. If you don't believe it you should > just take a look at the erratas on developer.intel.com - although you > should know that some of this stuff may severly alter your life and, > specifically, the way you go about debugging problems. Sometimes, > ignorance is bliss. :-) Not this one: http://sucs.swan.ac.uk/~cmckenna/humour/computer/potato.html But seriously, most relatively complicated hardware is buggy in some way. What matters is how the manufacturer is willing to deal with the problem. Intel at least has the sense to recall products with serious bugs that affect many people (i.e. Windows doesn't have a workaround for them.) Granted, they're probably applying Ford-style reasoning, weighing the cost of the recall against the cost of settling the lawsuits. I spoke with a former ASUS employee a while ago about a memory corruption bug that affected several lines of their older motherboards. Apparently the company policy was to categorically deny the existence of the bug. I pointed ASUS to some documentation of the problem from Adobe and Microsoft, and their reaction was, as expected, that the problem was with Windows and most Adobe software products. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message