From owner-freebsd-hackers Sat Mar 14 09:48:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10116 for freebsd-hackers-outgoing; Sat, 14 Mar 1998 09:48:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (root@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10074 for ; Sat, 14 Mar 1998 09:48:14 -0800 (PST) (envelope-from perlsta@cs.sunyit.edu) Received: from win95.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id NAA07061 for ; Sat, 14 Mar 1998 13:50:03 GMT Message-ID: <010001bd4f70$f8381b80$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: Subject: ATAPI patch please? Date: Sat, 14 Mar 1998 12:45:23 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG is there some way to unwedge my ATAPI cdrom? i pressed the play button on it while it was being used by a program... the driver doesn't seem to like a manual override. rebooting is not a problem(just an irritation), but every process that tries to access the drive gets stuck in "D" state now. maybe on a long enough wait the driver could force a total reset of the device? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message