From: Henning Meier-Geinitz <henning@meier-geinitz.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb-users@lists.sourceforge.net
Subject: Re: [Linux-usb-users] USB scanner issue (Was: Re: Beaver in Detox!)
Date: Sat, 6 Dec 2003 19:49:01 +0100 [thread overview]
Message-ID: <20031206184901.GH2455@meier-geinitz.de> (raw)
In-Reply-To: <20031128182625.GP2541@stop.crashing.org>
Hi,
On Fri, Nov 28, 2003 at 11:26:25AM -0700, Tom Rini wrote:
> On Wed, Nov 26, 2003 at 12:55:00PM -0800, Linus Torvalds wrote:
>
> [snip]
> > I give you "Beaver in Detox", aka linux-2.6.0-test11. This is mainly
> > brought on by the fact that the old aic7xxx driver was broken in -test10,
> > and Ingo found this really evil test program that showed an error case in
> > do_fork() that we had never handled right. Well, duh!
>
> I've found an odd problem that's in at least 2.6.0-test11.
Did it happen in older versions of Linux? I haven't heard of any
similar bug reports until now.
> I've
> reproduced this twice now with an Epson 1240 USB scanner
> (0x04b8/0x010b). What happens is if I run xsane from gimp, acquire a
> preview, start to scan and then cancel, the scanner becomes
> unresponsive.
This may be a bug in the plustek backend which supports that scanner.
The cancel handling is pretty complicated with some scanners.
> If I try and quit xsane, it gets stuck.
That sometimes happens with other scanners, too. E.g. some don't like
to get a "stop scan" command in certain situations. They just hang
after that command and further commands run into the USB timeout.
> Unplugging /
> replugging and then trying to kill xsane locked the machine up hard.
Well, obviously that should't happen. But it's really hard to debug
without any oops. There was a bug in the scanner driver that occured
when a device was open, then unplugged and then an application wrote
to it. But it's fixed since some time.
Does the freeze also happen if no other USB devices are attached? I guess
working without a keyboard is not that easy but it may be worth a test.
Otherwise I don't have any ideas.
Bye,
Henning
next prev parent reply other threads:[~2003-12-06 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 20:55 Beaver in Detox! Linus Torvalds
2003-11-26 22:00 ` Rik van Riel
2003-11-27 0:20 ` Beaver in Detox! (compile stats) John Cherry
2003-11-28 18:26 ` USB scanner issue (Was: Re: Beaver in Detox!) Tom Rini
2003-12-01 19:21 ` Greg KH
2003-12-01 20:52 ` Tom Rini
2003-12-09 17:41 ` Greg KH
2003-12-06 18:49 ` Henning Meier-Geinitz [this message]
2003-12-07 4:48 ` Tom Rini
2003-12-07 10:21 ` [Linux-usb-users] " Henning Meier-Geinitz
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=20031206184901.GH2455@meier-geinitz.de \
--to=henning@meier-geinitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).