From owner-freebsd-questions  Wed Dec 18 11:28:56 1996
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id LAA22957
          for questions-outgoing; Wed, 18 Dec 1996 11:28:56 -0800 (PST)
Received: from gdi.uoregon.edu (cisco-ts12-line3.uoregon.edu [128.223.150.135])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA22952
          for <questions@freebsd.org>; Wed, 18 Dec 1996 11:28:53 -0800 (PST)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.2/8.6.12) with SMTP id LAA00299; Wed, 18 Dec 1996 11:28:18 -0800 (PST)
Date: Wed, 18 Dec 1996 11:28:17 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: dwhite@resnet.uoregon.edu
To: Nadav Eiron <nadav@barcode.co.il>
cc: questions@freebsd.org
Subject: Re: ATAPI CD-related lockup? (fwd)
In-Reply-To: <Pine.BSF.3.91.961218195258.279A-100000@gatekeeper.barcode.co.il>
Message-ID: <Pine.BSI.3.94.961218112219.247D-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 18 Dec 1996, Nadav Eiron wrote:

> This seems to happen only on a machine with a CMD640-based controller. I 
> thought it was safe to use if you I only use one channel, but it seems 
> that even two devices on the primary channel can get it to hang. Does 
> anyone have experience with this problem? Does it only happen with a 
> HD+CDROM or will two HDs cause the same problems?

I have two hard disks hanging off a CMD 0x640 here and it works fine.  The
CMD's are known rogues on some systems.  Your best solution,
unfortunately, is to buy a IDE controller and connect your stuff to that
and disable the onboard.  If you do that, stay miles away from the Promise
stuff and you should be OK.  

> Does anyone have any information on what hacking is required to get the
> CMD 640 to work? 

Normally, it's transparent and included in the wdc controller.  Unless
someone wanted to hack up a specific driver for it I doubt we'll see
anything come of it.

Just a hunch, but check the IRQs and make sure the Ethernet card
isn't using IRQ 15 or 14.  

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major