Hello,

just a question regarding the handling of XS_SELTIMEOUT in scsi_ioctl.c.

I ran into the problem of getting error like

"uk0: unknown error category from host adapter code"

from scsi_ioctl.c when I added a scanner (Umax Stra 1200S) to my FreeBSD 3.0 (very) current system. This caused some followup problems in sane.

After digginig a little bit into this, it looks like the ncr.c driver gives back a status of XS_SELTIMEOUT for some status inquiries, which are not handled in routine scsi_usr_done in scsi_ioctl.c. This causes the above error-message.

Question: Is this intended? Should XS_SELTIMEOUT be handled here?

For me all the problems (with the exception of a couple of core-dumps in the gtk-frontend of sane) go away if I handle XS_SELTIMEOUT the same as XS_TIMEOUT in scsi_user_done. Will this cause some problems in other cases?

Michael

This is the patch I am using: *** scsi_ioctl.c Sun Apr 19 17:50:00 1998 --- scsi_ioctl.c.NEW Sun Apr 19 17:49:49 1998 *************** *** 121,126 **** --- 121,127 ---- break;

case XS_TIMEOUT: + case XS_SELTIMEOUT: SC_DEBUG(xs->sc_link,SDEV_DB3,("timeout\n")); screq->retsts = SCCMD_TIMEOUT; break;

To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message