Hi all,

In the course of various screwing around with my ATAPI CDROM device (including some dvd ripping and playing that got aborted at odd moments), I got the following messages:

Sep 25 20:50:07 vulcan kernel: acd0: WARNING - SETFEATURES SET TRANSFER MODE 
taskqueue timeout - completing request directly
Sep 25 20:50:07 vulcan kernel: acd0: timeout waiting to issue command
Sep 25 20:50:07 vulcan kernel: acd0: error issuing SETFEATURES SET TRANSFER 
MODE command
Sep 25 20:50:07 vulcan kernel: acd0: TIMEOUT - REQUEST_SENSE retrying (1 retry 
left)
Sep 25 20:50:18 vulcan kernel: acd0: WARNING - SETFEATURES SET TRANSFER MODE 
taskqueue timeout - completing request directly
Sep 25 20:50:18 vulcan kernel: acd0: timeout waiting to issue command
Sep 25 20:50:18 vulcan kernel: acd0: error issuing ATA PACKET command
Sep 25 20:50:18 vulcan kernel: acd0: TIMEOUT - REQUEST_SENSE retrying (0 
retries left)
Sep 25 20:50:29 vulcan kernel: acd0: WARNING - SETFEATURES SET TRANSFER MODE 
taskqueue timeout - completing request directly
Sep 25 20:50:29 vulcan kernel: acd0: timeout waiting to issue command
Sep 25 20:50:29 vulcan kernel: acd0: error issuing ATA PACKET command
Sep 25 20:50:29 vulcan kernel: acd0: FAILURE - REQUEST_SENSE timed out
Sep 25 20:50:29 vulcan kernel: (cd0:ata0:0:0:0): lost device
Sep 25 20:50:29 vulcan kernel: (cd0:ata0:0:0:0): removing device entry
Sep 25 20:50:29 vulcan kernel: (probe0:ata0:0:0:0): Lost target 0???
Sep 25 20:50:45 vulcan kernel: acd0: WARNING - SETFEATURES SET TRANSFER MODE 
taskqueue timeout - completing request directly
Sep 25 20:50:45 vulcan kernel: acd0: timeout waiting to issue command
Sep 25 20:50:45 vulcan kernel: acd0: error issuing ATA PACKET command
Sep 25 20:50:45 vulcan kernel: acd0: FAILURE - TEST_UNIT_READY timed out

I also have atapicam in use for DVD burning, and I now find that /dev/cd0 is missing, and I can't figure out how to get it back. "camcontrol rescan all" completes successfully, and I have

vulcan# camcontrol devlist
<DVDRW IDE 16X A07J>               at scbus1 target 0 lun 0 ()

But I can't seem to do anything with the device:

vulcan# camcontrol inquiry cd0
camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed
cam_lookup_pass: No such file or directory
cam_lookup_pass: either the pass driver isn't in your kernel
cam_lookup_pass: or cd0 doesn't exist
vulcan# camcontrol inquiry 1:0
camcontrol: cam_open_btl: no passthrough device found at 1:0:0

All the relevant devices are in my kernel, and always have been:

# ATA and ATAPI devices
device          ata
device          atadisk         # ATA disk drives
#device         ataraid         # ATA RAID drives
device          atapicd         # ATAPI CDROM drives
#device         atapifd         # ATAPI floppy drives
#device         atapist         # ATAPI tape drives
options         ATA_STATIC_ID   # Static device numbering
device          atapicam        # emulate ATAPI devices as SCSI ditto via CAM
                                # needs CAM to be present (scbus & pass)
# SCSI Controllers
# SCSI peripherals
device          scbus           # SCSI bus (required for SCSI)
#device         ch              # SCSI media changers
device          da              # Direct Access (disks)
#device         sa              # Sequential Access (tape etc)
device          cd              # CD
device          pass            # Passthrough device (direct SCSI access)
device          ses             # SCSI Environmental Services (and SAF-TE)

I also tried restarting /etc/rc.d/devfs and devd without effect, as well as "cdcontrol reset", and "camcontrol reset all".

Any suggestions on how to recover my cd0 device so I can use it again? I suspect rebooting would fix it, but I would rather avoid rebooting this machine as it handles a number of important tasks.

Thanks in advance. I'd appreciate a personal CC on any replies, if convenient, so I don't miss them in my digest.

--
Nate Eldredge
[EMAIL PROTECTED]
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to