From owner-freebsd-bugs Thu Oct 26 2: 7: 2 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 6F92437B479 for ; Thu, 26 Oct 2000 02:07:00 -0700 (PDT) Received: (from toddpw@localhost) by kamidake.apricot.com (8.8.8/8.8.8) id CAA16942; Thu, 26 Oct 2000 02:06:10 -0700 (PDT) From: "Todd P. Whitesel" Message-Id: <200010260906.CAA16942@kamidake.apricot.com> Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10) In-Reply-To: <200010252047.WAA17888@freebsd.dk> from Soren Schmidt at "Oct 25, 0 10:47:58 pm" To: sos@freebsd.dk (Soren Schmidt) Date: Thu, 26 Oct 2000 02:06:09 -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, 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. ok. Looks like you were right about one of memories, when I got home tonight one of the machines had rebooted itself AND it was sitting at the BIOS screen with "Memory test fail" at the bottom. > Hmm, if you can get access to some different brands of memory that could > shed some new light on this... Will do. In the meantime I am going to keep stressing the other memory module and see if I can get it to fail the BIOS test as well. That's my proof when I take it back for warranty replacement. (again! FRY'S MEMORY SUCKS!!) -- 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