From edward@edcom.com  Thu Apr 20 02:01:14 1995
Received: from edcom.com (edcom.com [140.174.173.185])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA23203
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 20 Apr 1995 02:01:12 -0700
Received: (from edward@localhost) by edcom.com (8.6.11/8.6.9) id CAA01861; Thu, 20 Apr 1995 02:01:05 -0700
Message-Id: <199504200901.CAA01861@edcom.com>
Date: Thu, 20 Apr 1995 02:01:05 -0700
From: Edward Wang <edward@edcom.com>
Reply-To: edward@edcom.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: xcdplayer crashes machine
X-Send-Pr-Version: 3.2

>Number:         353
>Category:       kern
>Synopsis:       xcdplayer crashes machine (with NCR810 SCSI)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    se
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Apr 20 02:10:03 1995
>Closed-Date:    Sun Dec 15 16:06:05 PST 1996
>Last-Modified:  Sun Dec 15 16:12:25 PST 1996
>Originator:     Edward Wang
>Release:        FreeBSD 2.1.0-Development i386
>Organization:
>Environment:

	950322-SNAP, NCR810 SCSI
	The drive is "SONY CD-ROM CDU-8012 3.1a", which is an old
	Sun external CDROM box.

>Description:

	Ejecting the CD in xcdplayer (using the eject control
	in the program) sometimes causes a timeout (or so I infer),
	followed by a scsi reset that doesn't quite recover.
	At this point, the machine dies with all scsi commands failing.
	One consequence is the inability to sync before reboot.
	Another is not being able to switch to ttyv0 (if any paging
	of the X server is involved) and see the error messages.

	The problem is most likely not caused by xcdplayer itself.

>How-To-Repeat:

	xcdplayer
	click on the eject box
	wait

>Fix:
	
	If someone wants to debug this, I can try to repeat and
	get the kernel messages and some more data.
	As it is, since it's a particularly nasty crash, I don't
	want to mess with it too much.  I did try it twice to make
	sure it wasn't a fluke.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->wolf 
Responsible-Changed-By: scrappy 
Responsible-Changed-When: Fri Apr 12 22:14:26 PDT 1996 
Responsible-Changed-Why:  
Responsible-Changed-From-To: wolf->se 
Responsible-Changed-By: scrappy 
Responsible-Changed-When: Wed Apr 17 16:21:31 PDT 1996 
Responsible-Changed-Why:  
assigned to wrong person first time through 
State-Changed-From-To: open->closed 
State-Changed-By: se 
State-Changed-When: Sun Dec 15 16:06:05 PST 1996 
State-Changed-Why:  
Originator is still at old software level (2.0-SNAP-950322), 
and can't check whether the time-out fixes that went into 
the driver actually solved this problem (as I assume). 
Since there was no other report of a similar problem for 
more than one and a half year, this PR will be closed. 
>Unformatted:


