> After the first program is finished, any attempt to access the
> scanner will fail until rebooting the system. At this time the
> message "tagged command queue depth set to 2" shows up in the
> system logs. From there on, the NCR driver obviously is busy
> resetting the SCSI bus:
>
> Oct 4 16:29:02 swamp kernel: ncr53c810-0-<5,0>: tagged command queue depth set to 2
Using tags with a scanner is very optimistic. ;-)
The driver normally catches this feature from the INQUIRY response.
Could you send me the INQUIRY response sent by the scanner?
You can get it using scsiinfo or scsi-config tool.
> Oct 4 16:33:11 swamp kernel: ncr53c810-0-<5,*>: asynchronous.
> Oct 4 16:34:12 swamp kernel: ncr53c810-0: restart (scsi reset).
> Oct 4 16:34:12 swamp kernel: ncr53c810-0-<5,*>: asynchronous.
> Oct 4 16:34:56 swamp kernel: ncr53c810-0-<5,0>: COMMAND FAILED (8a ff) @c009a820.
> Oct 4 16:36:34 swamp kernel: ncr53c810-0-<5,0>: M_REJECT received (75:8).
> Oct 4 16:36:34 swamp kernel: ncr53c810-0-<5,0>: M_REJECT received (75:8).
> Oct 4 16:36:49 swamp kernel: ncr53c810-0-<5,0>: tagged command queueing disabled
Normal breakage if the device does not support tags.
> When I disable tagged command queueing, I don't get the "depth
> set to 2" - message, but otherwise things are the same. The only
> workaround I could find is to remove the scanner via
> "remove-single-device" and immediately add it again after every
> program run. The problem is obviously caused by the current
> version of the ncr driver (Kernel 2.1.125) - when I boot an
> ancient kernel (2.1.59), the scanner works alright.
Nothing is really obvious with SCSI, except that there is bunches of
non-compliant SCSI devices floating around. Drivers 2.x only may use tags
with hard disks that claim the feature. Recent drivers use tags with any
device that responds to INQUIRY (EVPD and CmDt not set) with appropriate
response data format and claiming this feature.
Do you get the exact same error messages as above when the error occurs
and tags are disabled?
Gerard.
PS: Could you move this discussion to linux-scsi, please.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/