From owner-freebsd-bugs Wed Oct 25 2: 8:17 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 BEB5B37B479 for ; Wed, 25 Oct 2000 02:08:11 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA52929; Wed, 25 Oct 2000 11:06:13 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200010250906.LAA52929@freebsd.dk> Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10) In-Reply-To: <200010250850.BAA36380@freefall.freebsd.org> from "Todd P. Whitesel" at "Oct 25, 2000 01:50:01 am" To: toddpw@apricot.com (Todd P. Whitesel) Date: Wed, 25 Oct 2000 11:06:12 +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: > After two days of success, the PIO-only tests have exhibited similar failures > on both FreeBSD 4.1.1 and NetBSD 1.5_ALPHA2. > > So that would suggest that this is not a strictly UDMA issue after all, > but some subtle problem with the VIA 133 chipset... yuck. 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... Try some other memory or if possible relax the RAM timing in the BIOS... Do you pr chance run it with 133Mhz mem ? if so is it really PC133 mem you have ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message