public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam <genlogic@mediaone.net>
To: linux-kernel@vger.kernel.org
Subject: scsi acard AEC6712D and atp870u.c driver
Date: Fri, 21 Dec 2001 19:10:46 -0500	[thread overview]
Message-ID: <3C23CF86.6010600@mediaone.net> (raw)

*please cc the answers to me*


hello

i am using an acer scanwit scanner which comes with the acard AEC6712D 
scsi controller.
i am also using the acard driver in 2.4.7 (also tried 2.4.13). ejecting 
the scanner seems to work (no data sent),
but scanning and previewing seems to cause problems.

it seems to be the driver that is causing the problems. when it 
eventually times out,
i get:

scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0, 
lun 0 Write (10) 00 82 00 00 01 00 1d e2 00
working=1 last_cmd=0  quhdu=1a quendu=1a  r 0= a r 1=2c r 2=cf r 3=2a r 
4= 0 r 5=82 r 6= 0 r 7= 0 r 8= 1 r 9= 0 r a=1d r b=e2 r c= 0 r d= 0 r e= 
0 r f= 0 r10=3a r11=20 r12= 0 r13= 0 r14= 2 r15=20 r16=80 r1c= 0 r1f=35 
in_snd= 0  r20= 1 r22= 8 r3a=2b
 r3b=20

 que cdb=  2a   0  82   0   0   1   0  1d  e2   0  last_lenu= 1de2

i have gotten some suggestions such as

removing

      if (dev->ata_cdbu[0] == READ_CAPACITY) {
        if (workrequ->request_bufflen > 8) {
                workrequ->request_bufflen = 0x08;
        }
      }

from the driver code, but this just causes the target id (as seen above to be: 0) to be the last command
so the command it got before was 0xff

as seen from
if ((j & 0x40) != 0)
		{
		     if (dev->last_cmd == 0xff)
		     {
			dev->last_cmd = target_id;
		     }
		     dev->last_cmd |= 0x40;
		}

any ideas on what the problem might be? when was the lastest bug update on atp870u.c?


thanx,

*please cc the answers to me*

--sam



                 reply	other threads:[~2001-12-22  0:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C23CF86.6010600@mediaone.net \
    --to=genlogic@mediaone.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox