Date: Thu, 06 Apr 2000 10:26:13 +0300 From: Maxim Sobolev <sobomax@altavista.net> To: Soren Schmidt <sos@freebsd.dk> Cc: Jon Hamilton <hamilton@pobox.com>, current@FreeBSD.ORG Subject: Re: Dangerously looking glitch (4.0-STABLE) Message-ID: <38EC3C14.2471F70@altavista.net> References: <200004051431.QAA47392@freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Soren Schmidt wrote: > 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... Soren, I apologise for blaming your ata, it seems that it is not it, because when I switched back to the old wd it brought the same unpleasant result. I've also check the cable by replacing it with another and trying to plug it firmly, but it also did not solve the problem. Could you as a HDD expert suggest the way to track it down? Maybe you had previously seen any problems of that sort. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38EC3C14.2471F70>