From owner-freebsd-bugs Wed Oct 25 13:49:58 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 69A1D37B479 for ; Wed, 25 Oct 2000 13:49:55 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA17888; Wed, 25 Oct 2000 22:47:58 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200010252047.WAA17888@freebsd.dk> Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10) In-Reply-To: <200010251957.MAA10138@kamidake.apricot.com> from "Todd P. Whitesel" at "Oct 25, 2000 12:57:16 pm" To: toddpw@apricot.com (Todd P. Whitesel) Date: Wed, 25 Oct 2000 22:47:58 +0200 (CEST) Cc: freebsd-bugs@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-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Todd P. Whitesel wrote: > > Hmm, having looked at the description again I dont see you getting any > > failures from the ATA driver (ie timeouts etc), so I think this is > > a memory problem after all, which is consistent with SEGV's etc... > > That's what I thought at first, but I already replaced one of the memories > because it was clearly bad -- I actually have two identically configured > machines here and they both exhibit the same symptoms. Hmm, If you dont get ICRC errors from the ata driver, you are not getting corrupt data off the disk, that means the corruptions must be somewhere else. Having using DMA escalate the problem, suggest memory problems also. > > Try some other memory or if possible relax the RAM timing in the BIOS... > > SDRAM Timing: 2 or 3, and it is already set to 3. > > > Do you pr chance run it with 133Mhz mem ? if so is it really PC133 > > mem you have ? > > The memory is labelled PC133 and that's what I asked for. (It's Fry's memory, > oh no!) > > I also tried the tests at "HOSTCLK-33" to see if 100mhz would work better, > but it got the same failures. Hmm, if you can get access to some different brands of memory that could shed some new light on this... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message