Bug 12358 - USB scanner becomes unavailable after first use
Summary: USB scanner becomes unavailable after first use
Status: RESOLVED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-04 08:16 UTC by Darko Sokolić
Modified: 2009-04-05 00:50 UTC (History)
0 users

See Also:
Kernel Version: 2.6.28
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description Darko Sokolić 2009-01-04 08:16:24 UTC
Latest working kernel version: 2.6.27.10
Earliest failing kernel version: 2.6.28
Distribution: Mandria 2009.0
Hardware Environment: Epson DX7450 (printer/scanner/card reader over USB connected to ASUS P5Q PRO motherboard
Software Environment:
 from Mandriva:
  sane-backends-1.0.19-7mdv2009.0
  saned-1.0.19-7mdv2009.0
  xsane-0.995-2mdv2009.0
  libksane0-4.1.3-1.1mdv2009.0
  libsane1-1.0.19-7mdv2009.0
  sane-frontends-1.0.14-5mdv2009.0
 from Epson/Avasys
  iscan-2.11.0-1.c2.i386.rpm (it conflicts with libsane1 since day one, I let this one to overwrite libsane file)
Problem Description:
 
Mentioned printer/scanner works fine witjh 2.6.27.10.
After moving to 2.6.28. scanner cannot be used - attempting to scan will report some sort of errors like if scanner is not present.
Listing scanners with "scanimage -L" reports scanner correctly only when called first time after boot, and before any attempt to use the scanner.
Following invocations of the sam command will report that no scanners are found.

Steps to reproduce:
Following are steps I did that reporoduce the problem in my environment. I took some peaces of information that might be helpfull.
This is probably not precise enough to pinpoint the problem - please advise me about additional information you need and how to obtain it.

After turning on device, following kernel messages appear (as shown by dmesg):
usb 2-4: new high speed USB device using ehci_hcd and address 4
usb 2-4: configuration #1 chosen from 1 choice
usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0838
scsi8 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb 2-4: New USB device found, idVendor=04b8, idProduct=0838
usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-4: Product: USB2.0 MFP(Hi-Speed)
usb 2-4: Manufacturer: EPSON
usb 2-4: SerialNumber: 4C39313036480600D4
scsi 8:0:0:0: Direct-Access     EPSON    Stylus Storage   1.00 PQ: 0 ANSI: 2
sd 8:0:0:0: [sdc] Attached SCSI removable disk
sd 8:0:0:0: Attached scsi generic sg4 type 0
usb-storage: device scan complete


Invoking "scanimage -L" gives following:
device `epkowa:libusb:002:004' is a Epson Stylus CX7300/CX7400/DX7400 flatbed scanner

This is appended to dmesg:
usbl0p: removed
usb 2-4: usbfs: interface 2 claimed by usb-storage while 'scanimage' sets config #1
usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0838
ppdev: user-space parallel port driver
ppdev0: no associated port!

Now, if we invoke "scanimage -L" again, we get this error:
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).


This are additional lines of dmesg:
usblp0: removed
usb 2-4: usbfs: interface 2 claimed by usb-storage while 'scanimage' sets config #1
usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0838
ppdev0: no associated port!

Note: I my opinion, internal hub in Epson DX7450 apparently behaves like if one part (printer or scanner) is used, other appears temporarily disconnected. Could this be related to bug 11921 ?
Comment 1 Anonymous Emailer 2009-01-05 15:47:57 UTC
Reply-To: akpm@linux-foundation.org


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Sun,  4 Jan 2009 08:16:27 -0800 (PST)
bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=12358
> 
>            Summary: USB scanner becomes unavailable after first use
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.28
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: USB
>         AssignedTo: greg@kroah.com
>         ReportedBy: darko.sokolic@zg.t-com.hr
> 
> 
> Latest working kernel version: 2.6.27.10
> Earliest failing kernel version: 2.6.28

regression.

> Distribution: Mandria 2009.0
> Hardware Environment: Epson DX7450 (printer/scanner/card reader over USB
> connected to ASUS P5Q PRO motherboard
> Software Environment:
>  from Mandriva:
>   sane-backends-1.0.19-7mdv2009.0
>   saned-1.0.19-7mdv2009.0
>   xsane-0.995-2mdv2009.0
>   libksane0-4.1.3-1.1mdv2009.0
>   libsane1-1.0.19-7mdv2009.0
>   sane-frontends-1.0.14-5mdv2009.0
>  from Epson/Avasys
>   iscan-2.11.0-1.c2.i386.rpm (it conflicts with libsane1 since day one, I let
> this one to overwrite libsane file)
> Problem Description:
> 
> Mentioned printer/scanner works fine witjh 2.6.27.10.
> After moving to 2.6.28. scanner cannot be used - attempting to scan will
> report
> some sort of errors like if scanner is not present.
> Listing scanners with "scanimage -L" reports scanner correctly only when
> called
> first time after boot, and before any attempt to use the scanner.
> Following invocations of the sam command will report that no scanners are
> found.
> 
> Steps to reproduce:
> Following are steps I did that reporoduce the problem in my environment. I
> took
> some peaces of information that might be helpfull.
> This is probably not precise enough to pinpoint the problem - please advise
> me
> about additional information you need and how to obtain it.
> 
> After turning on device, following kernel messages appear (as shown by
> dmesg):
> usb 2-4: new high speed USB device using ehci_hcd and address 4
> usb 2-4: configuration #1 chosen from 1 choice
> usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x04B8 pid
> 0x0838
> scsi8 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 4
> usb-storage: waiting for device to settle before scanning
> usb 2-4: New USB device found, idVendor=04b8, idProduct=0838
> usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 2-4: Product: USB2.0 MFP(Hi-Speed)
> usb 2-4: Manufacturer: EPSON
> usb 2-4: SerialNumber: 4C39313036480600D4
> scsi 8:0:0:0: Direct-Access     EPSON    Stylus Storage   1.00 PQ: 0 ANSI: 2
> sd 8:0:0:0: [sdc] Attached SCSI removable disk
> sd 8:0:0:0: Attached scsi generic sg4 type 0
> usb-storage: device scan complete
> 
> 
> Invoking "scanimage -L" gives following:
> device `epkowa:libusb:002:004' is a Epson Stylus CX7300/CX7400/DX7400 flatbed
> scanner
> 
> This is appended to dmesg:
> usbl0p: removed
> usb 2-4: usbfs: interface 2 claimed by usb-storage while 'scanimage' sets
> config #1
> usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x04B8 pid
> 0x0838
> ppdev: user-space parallel port driver
> ppdev0: no associated port!
> 
> Now, if we invoke "scanimage -L" again, we get this error:
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
> 
> 
> This are additional lines of dmesg:
> usblp0: removed
> usb 2-4: usbfs: interface 2 claimed by usb-storage while 'scanimage' sets
> config #1
> usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x04B8 pid
> 0x0838
> ppdev0: no associated port!
> 
> Note: I my opinion, internal hub in Epson DX7450 apparently behaves like if
> one
> part (printer or scanner) is used, other appears temporarily disconnected.
> Could this be related to bug 11921 ?
> 
Comment 2 Anonymous Emailer 2009-01-06 02:25:14 UTC
Reply-To: oliver@neukum.org

Am Tuesday 06 January 2009 00:47:24 schrieb Andrew Morton:
> > Latest working kernel version: 2.6.27.10
> > Earliest failing kernel version: 2.6.28
> 
> regression.

Looks like bug 12301. Please try the patch attached to that bug.

	Regards
		Oliver
Comment 3 Darko Sokolić 2009-01-11 06:05:17 UTC
Tried patch from bug 12303 and it works.
Repeated once again on "plain" kernel 2.6.28 and it fails.
So, patch works!
Thank you.
Comment 4 Darko Sokolić 2009-01-11 09:14:21 UTC
Correction - pach that works is from bug 12301. Sorry...
>   
Comment 5 Alan Stern 2009-01-12 13:17:43 UTC
So this bug report can be rejected as a duplicate of #12301.
Comment 6 Darko Sokolić 2009-04-05 00:50:16 UTC
I can confirm that in 2.6.29 problem is resolved.

I will also close this bug (am I supposed to to this?)

Note You need to log in before you can comment on or make changes to this bug.