All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI scanner problem with all kernels since 2.3.42
Date: Tue, 09 Jan 2001 15:53:02 -0500	[thread overview]
Message-ID: <3A5B7A2E.E3F964A8@torque.net> (raw)

Tim Waugh wrote:
> I'm having problems with using xsane to acquire a preview from an HP
> ScanJet 5P connected to an AHA-2940.  2.3.42 is the last kernel that
> works right for me.
> 
> The symptom is that the scanner starts to make scanning sounds, then
> stops, and xsane says 'Error during read: Error during device I/O'.

Tim and I have been looking at this offline. The significance
of lk 2.3.43 was the addition of a new sg driver that has an
additional interface. Recent versions of SANE use that newer
sg interface. The problem that Tim reported seemed to be caused
by timeouts ** resulting in scsi bus resets. Anyway the problem
seems to disappear with the recently released SANE 1.0.4 .
[The original report was based on SANE 1.0.3 and earlier.]

There is also a problem report with the  SnapScan 1236 <--> aha152x 
combination also based on SANE 1.0.3 . This one is looking 
like an "uninitialized errno" bug fixed in SANE 1.0.4 .

** SANE's newer sg interface shortens the per command timeout
from 10 minutes to 10 seconds. Most other OSes interfaces in
SANE have a timeout value of 1 minute or more. I suspect 10 
seconds may be too short.

Doug Gilbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-09 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 20:53 Douglas Gilbert [this message]
2001-01-10  1:44 ` SCSI scanner problem with all kernels since 2.3.42 Tim Waugh
2001-01-15 21:24 ` Juergen E Fischer
  -- strict thread matches above, loose matches on Subject: below --
2001-01-07  0:02 Tim Waugh

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=3A5B7A2E.E3F964A8@torque.net \
    --to=dougg@torque.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.