From owner-freebsd-bugs Wed Oct 25 12:58:11 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from kamidake.apricot.com (kamidake.apricot.com [64.121.160.36]) by hub.freebsd.org (Postfix) with ESMTP id 0E19C37B479 for ; Wed, 25 Oct 2000 12:58:08 -0700 (PDT) Received: (from toddpw@localhost) by kamidake.apricot.com (8.8.8/8.8.8) id MAA10138; Wed, 25 Oct 2000 12:57:16 -0700 (PDT) From: "Todd P. Whitesel" Message-Id: <200010251957.MAA10138@kamidake.apricot.com> Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10) In-Reply-To: <200010250906.LAA52929@freebsd.dk> from Soren Schmidt at "Oct 25, 0 11:06:12 am" To: sos@freebsd.dk (Soren Schmidt) Date: Wed, 25 Oct 2000 12:57:16 -0700 (PDT) Cc: toddpw@apricot.com, freebsd-bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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. > 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. -- Todd Whitesel Anime Expo Information at toddpw @ apricot.com http://www.anime-expo.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message