From owner-freebsd-bugs  Sat Feb  3 02:48:33 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA19472
          for bugs-outgoing; Sat, 3 Feb 1996 02:48:33 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA19467
          for <freebsd-bugs@freebsd.org>; Sat, 3 Feb 1996 02:48:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id CAA01243; Sat, 3 Feb 1996 02:48:24 -0800
To: swise@austin.ibm.com (Jean-Steveau Wise)
cc: freebsd-bugs@freebsd.org
Subject: Re: ATAPI 4x cdrom hang 
In-reply-to: Your message of "Fri, 02 Feb 1996 23:02:10 CST."
             <9602030502.AA28851@vikings.austin.ibm.com> 
Date: Sat, 03 Feb 1996 02:48:24 -0800
Message-ID: <1241.823344504@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-bugs@freebsd.org
Precedence: bulk

> I've got a 133MHZ Intel system (Packard Bell) with a 4x IDE ATAPI
> cdrom.  FreeBSD 2.1 finds the device and I can read from it (ls -sailR
> will show everything on the cd mounted).  However, whenever I try to
> transfer anything off it, the entire system hangs.  I'd be happy to get

Hmmmm.  First thing to start might be to compile DDB into your kernel.
See http://www.freebsd.org/handbook/handbook220.html#403 for a quick
reference on using the kernel debugger.  Then when it hangs next time,
you can drop into DDB and at least figure out where it's hanging!
Perhaps you're looping somewhere in the ATAPI driver and can add a
check to catch some case it's missing.

The driver's author has disappeared without a trace, I'm afraid to
say, so we're currently sort of winging it with this one until he
makes his reappearance! :-(

					Jordan