From owner-freebsd-hardware Thu Feb 21 17:14:49 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from orac.moffetimages.com (dsl3-63-249-88-4.cruzio.com [63.249.88.4]) by hub.freebsd.org (Postfix) with ESMTP id E19D837B402 for ; Thu, 21 Feb 2002 17:14:41 -0800 (PST) Received: from DIABLO.moffetimages.com (dhcp-64.moffetimages.com [192.168.20.64]) (authenticated bits=0) by orac.moffetimages.com (8.12.1/8.12.1) with ESMTP id g1M1EeHm018559 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 21 Feb 2002 17:14:41 -0800 (PST) Message-Id: <5.1.0.14.2.20020221170615.03751c38@orac.moffetimages.com> X-Sender: brianm@orac.moffetimages.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 21 Feb 2002 17:18:21 -0800 To: freebsd-hardware@freebsd.org From: "Brian D. Moffet" Subject: SAN Disk Flash ram Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I am using a Flash Ram, connected to a device that converts the PCM/CIA Flash ram to an IDE interface, it looks like a 30 Meg hard drive... It is currently hooked to the slave side of my second IDE controller (ASUS CUV4X-E motherboard with Pentium III 880 Mghz), and running FreeBSD 4.3. After doing the usual fdisk, disklabel, newfs, I mount it and start taring stuff to the flash ram. Someplace in the middle of this, the machine will lock up completely. Where it locks up is not consistent. The keyboard is inactive, as determined by no change in LEDs. The IDE light is on continuously. I let it sit for a few hours before I shut the machine down. I have put a 40pin/80 conductor IDE connector on both channels rather than the 40pin/40 conductor that was in there, but that didn't help. Is there a debug flag or something that I can turn on to help track state information in the driver, so that I can try to determine what is going on? I'm just looking for ways to start tracking this problem, though if anyone already knows of a solution, great. I am going to try it under LINUX (redhat 7.0) to see if I can reproduce the problem. Thanks much, Brian Moffet Brian D. Moffet brianm@moffetimages.com -- http://www.moffetimages.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message