From owner-freebsd-current Wed Apr 5 7:32:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1B7DD37B6FC for ; Wed, 5 Apr 2000 07:32:15 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA47392; Wed, 5 Apr 2000 16:31:41 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004051431.QAA47392@freebsd.dk> Subject: Re: Dangerously looking glitch (4.0-STABLE) In-Reply-To: <38EB3E8C.7E9ACA94@altavista.net> from Maxim Sobolev at "Apr 5, 2000 04:24:29 pm" To: sobomax@altavista.net (Maxim Sobolev) Date: Wed, 5 Apr 2000 16:31:40 +0200 (CEST) Cc: hamilton@pobox.com (Jon Hamilton), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: > > I've tried it on my home machine and failed to reproduce also. However it is > strange, because if it is the CPU/Memory problem, then there should be other signs > - random applications crashes, spontaneous reboots etc., but machine is pretty > stable - up and running for weeks since 4.0-REL w/o any notable problems. On the > other hand if it is HDD problem or problem with its cable, then there should also > be some signs. I've never seen this problem on the same hardware under 2.* and 3.* > during past 1.5 years. Maybe it is ata driver, because it is the only thing that is > known not very extensively tested (and has already acknoweleged problems with some > hardware). I'll try to fallback to the wd and look what will happen. Uhm what acknowledged problems is that ? I know of no cases of data corruption in this way, its all pretty much go/nogo situations... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message