On Tue, 27 Nov 2007, Vasilis Vasaitis wrote:
> On Mon, Nov 26, 2007 at 09:57:30AM -0500, Alan Stern wrote:
> >
> > All right. What shows up in /proc/bus/usb/devices after you plug in
> > the camera under KDE? Note: not all distributions mount the filesystem
> > containing that file; you may need to do it by hand:
> >
> > mount -t usbfs none /proc/bus/usb
>
> I get this entry:
>
> T: Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#= 16 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=04da ProdID=2372 Rev= 0.10
> S: Manufacturer=Panasonic
> S: Product=DMC-FZ7
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
> I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
> E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
The key item here is the "Driver=(none)" field. Something has unbound
usb-storage from the device, probably via usbfs.
> > Also, what shows up in the output from "ps -Awf"?
>
> A set of kioslaves, here's one capture (not very helpful I know):
>
> mod 14936 18636 0 01:45 ? 00:00:00 kio_system [kdeinit] system /tmp/ksocket-mod/klauncherXZ7X
> mod 14937 18636 0 01:45 ? 00:00:00 kio_media [kdeinit] media /tmp/ksocket-mod/klauncherXZ7Xhb
> mod 14938 18636 0 01:45 ? 00:00:00 kio_file [kdeinit] file /tmp/ksocket-mod/klauncherXZ7Xhb.s
> mod 14939 18636 2 01:45 ? 00:00:00 kio_kamera [kdeinit] camera /tmp/ksocket-mod/klauncherXZ7X
> mod 14940 18636 2 01:45 ? 00:00:00 kio_kamera [kdeinit] camera /tmp/ksocket-mod/klauncherXZ7X
> mod 14946 18636 0 01:45 ? 00:00:00 kio_media [kdeinit] media /tmp/ksocket-mod/klauncherXZ7Xhb
> mod 14947 18636 0 01:45 ? 00:00:00 kio_file [kdeinit] file /tmp/ksocket-mod/klauncherXZ7Xhb.s
> mod 14948 18636 1 01:45 ? 00:00:00 kio_kamera [kdeinit] camera /tmp/ksocket-mod/klauncherXZ7X
I was looking for a usb-storage process, but it's evident that we won't
see one.
> I've also tried your usbcore.usbfs_snoop=y suggestion, and I've
> attached the kernel output when it's turned on to the bug page. Not
> sure if it's illuminating in any way. I'll also try Oliver's
> CONFIG_USB_DEBUG suggestion as soon as I find some time.
Boy, that output is hard to interpret. It leads me to wonder if the
dump is being done correctly... And unfortunately it doesn't include
the name of the current process. Well, we can fix that.
If you edit the kernel source file drivers/usb/core/devio.c, near the
start you'll see a definition of the snoop macro. Change it as
follows:
#define snoop(dev, format, arg...) \
do { \
if (usbfs_snoop) \
dev_info( dev , "%s: " format , \
current->comm , ## arg); \
} while (0)
That will include the process name in the log entries.
It wouldn't be surprising to find that the offending process is one of
those listed above, like kio_camera. It may think your camera is in
PTP mode even when that's not the case.
Alan Stern
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
linux-usb-devel@xxxxxxxxxxxxxxxxxxxxx
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[Home]
[Video for Linux]
[Photo]
[Yosemite Forum]
[Yosemite Photos]
[Video Projectors]
[PDAs]
[Hacking TiVo]
[Linux Kernel]
[Linux SCSI]
[XFree86]
[Devices]
[Big List of Linux Books]
[Free Dating]