[sane-devel] Question on old Mustek Scanner (12000SP)
Dieter Jurzitza
dieter.jurzitza@t-online.de
Sun, 29 May 2005 21:29:13 +0200
Dear listmembers,
I use a Mustek Scanner (since years) but now decided to upgrade my system f=
rom=20
SuSE 8.1 to (in the meantime) SuSE9.3)
I had had the scanner connected to the same SCSI-bus as the harddisk and th=
e=20
cdrom and the zip-drive, but in the meantime this became impossible.
So I added a second SCSI card (decided for the scanner and the zip drive) a=
nd=20
(in general) things work ok.
What does *not* work is start scans after a long sleep of the scanner:
from /proc/scsi/scsi:
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: FUJITSU Model: MAN3735MP Rev: 0109
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: TANDBERG Model: TDC 4100 Rev: =3D07:
Type: Sequential-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: TEAC Model: CD-ROM CD-532S Rev: 1.0A
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 05 Lun: 00
Vendor: IOMEGA Model: ZIP 100 Rev: J.02
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 06 Lun: 00
Vendor: SCANNER Model: Rev: 2.02
Type: Scanner ANSI SCSI revision: 01 CCS
from /var/log/messages:
May 25 13:14:01 djunix kernel: scsi1:0:5:0: Attempting to queue an ABORT=20
message
May 25 13:14:01 djunix kernel: CDB: 0x0 0x0 0x0 0x0 0x0 0x0
May 25 13:14:01 djunix kernel: scsi1: At time of recovery, card was not pau=
sed
May 25 13:14:01 djunix kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins=20
<<<<<<<<<<<<<<
<<<
May 25 13:14:01 djunix kernel: scsi1: Dumping Card State in Command phase, =
at=20
SEQADDR 0
x169
May 25 13:14:01 djunix kernel: Card was paused
May 25 13:14:01 djunix kernel: ACCUM =3D 0x80, SINDEX =3D 0xac, DINDEX =3D =
0xc0,=20
ARG_2 =3D 0x0
May 25 13:14:01 djunix kernel: HCNT =3D 0x0 SCBPTR =3D 0x0
May 25 13:14:01 djunix kernel: SCSISIGI[0x84]:(BSYI|CDI) ERROR[0x0]=20
SCSIBUSL[0xc0]=20
May 25 13:14:01 djunix kernel: LASTPHASE[0x80]:(CDI) SCSISEQ[0x12]:
(ENAUTOATNP|ENRSELI)
=20
May 25 13:14:01 djunix kernel: SBLKCTL[0x0] SCSIRATE[0x0] SEQCTL[0x10]:
(FASTMODE)=20
May 25 13:14:01 djunix kernel: SEQ_FLAGS[0x0] SSTAT0[0x7]:(DMADONE|SPIORDY|
SDONE)=20
May 25 13:14:01 djunix kernel: SSTAT1[0x2]:(PHASECHG) SSTAT2[0x0] SSTAT3[0x=
0]=20
SIMODE0[0
x0]=20
May 25 13:14:01 djunix kernel: SIMODE1[0xac]:(ENSCSIPERR|ENBUSFREE|ENSCSIRS=
T|
ENSELTIMO)
=20
May 25 13:14:01 djunix kernel: SXFRCTL0[0x88]:(SPIOEN|DFON) DFCNTRL[0x4]:
(DIRECTION)=20
May 25 13:14:01 djunix kernel: DFSTATUS[0x6d]:(FIFOEMP|DFTHRESH|HDONE|
=46IFOQWDEMP|DFCACH
ETH)=20
May 25 13:14:01 djunix kernel: STACK: 0x37 0xe5 0x163 0x1a4
May 25 13:14:01 djunix kernel: SCB count =3D 4
May 25 13:14:01 djunix kernel: Kernel NEXTQSCB =3D 1
May 25 13:14:01 djunix kernel: Card NEXTQSCB =3D 1
May 25 13:14:01 djunix kernel: QINFIFO entries:=20
May 25 13:14:01 djunix kernel: Waiting Queue entries:=20
May 25 13:14:01 djunix kernel: Disconnected Queue entries:=20
May 25 13:14:01 djunix kernel: QOUTFIFO entries:=20
May 25 13:14:01 djunix kernel: Sequencer Free SCB List: 1 2=20
May 25 13:14:01 djunix kernel: Sequencer SCB Info:=20
May 25 13:14:01 djunix kernel: 0 SCB_CONTROL[0x40]:(DISCENB)=20
SCB_SCSIID[0x57] SCB_LUN
[0x0]=20
May 25 13:14:01 djunix kernel: SCB_TAG[0x2]=20
May 25 13:14:01 djunix kernel: 1 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:
(TWIN_CHNLB|OID|TW
IN_TID)=20
May 25 13:14:01 djunix kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID)=20
SCB_TAG[0xff]=20
May 25 13:14:01 djunix kernel: 2 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:
(TWIN_CHNLB|OID|TW
IN_TID)=20
May 25 13:14:01 djunix kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID)=20
SCB_TAG[0xff]=20
May 25 13:14:01 djunix kernel: Pending list:=20
May 25 13:14:01 djunix kernel: 2 SCB_CONTROL[0x40]:(DISCENB)=20
SCB_SCSIID[0x57] SCB_LUN
[0x0]=20
May 25 13:14:01 djunix kernel: Kernel Free SCB list: 3 0=20
May 25 13:14:01 djunix kernel: Untagged Q(5): 2=20
May 25 13:14:01 djunix kernel: DevQ(0:5:0): 0 waiting
May 25 13:14:01 djunix kernel: DevQ(0:6:0): 0 waiting
May 25 13:14:01 djunix kernel:=20
May 25 13:14:01 djunix kernel: <<<<<<<<<<<<<<<<< Dump Card State Ends=20
>>>>>>>>>>>>>>>>>>
May 25 13:14:01 djunix kernel: scsi1:0:5:0: Device is active, asserting ATN
May 25 13:14:01 djunix kernel: Recovery code sleeping
May 25 13:14:06 djunix kernel: Recovery code awake
May 25 13:14:06 djunix kernel: Timer Expired
May 25 13:14:06 djunix kernel: aic7xxx_abort returns 0x2003
May 25 13:14:06 djunix kernel: scsi1:0:5:0: Attempting to queue a TARGET RE=
SET=20
message
May 25 13:14:06 djunix kernel: CDB: 0x0 0x0 0x0 0x0 0x0 0x0
May 25 13:14:06 djunix kernel: aic7xxx_dev_reset returns 0x2003
May 25 13:14:06 djunix kernel: Recovery SCB completes
=46rom then on I can scan 100 scans without further issues. Seems to me as =
if=20
somehow some timeouts became shorter than before? I use SuSE9.3 with kernel=
=20
2.6.11.4-20a-smp. Should those messages really bother me? However, they=20
do :-). I did not see similar issues with kernel 2.4.21 on the same scanner=
=20
and the same scsi-card using the same harddisk etc. Something must have=20
turned significantly faster than before.
Many thanks for any inputs,
take care
Dieter Jurzitza
=2D-=20
=2D----------------------------------------------------------
|
\
/\_/\ |
| ~x~ |/-----\ /
\ /- \_/
^^__ _ / _ ____ /
<=B0=B0__ \- \_/ | |/ | |
|| || _| _| _| _|
if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
=2D----------------------------------------------------------