On Fri, 12 Mar 2004, Alan Stern wrote: > > Something is different between 2.4.X and 2.6.X. Something in the iscan > > (which is provided by Epson) code seems to trigger the problem quick. > > (iscan also implements an "epkowa" driver in SANE). > > Also something is different between vuescan and iscan. I have no idea > what it might be, though.
Certainly, but as vuescan isn't open source and strace doesn't break the USBDEVFS bulk stuff down or present a hexdump or string as for read or write, I have no clues what this might be. iscan has proprietary object code linked but is otherwise GPL (most of it is SANE based) so we might get behind what it's doing. > That doesn't have a yes/no answer. usbdevfs is now (in 2.6) called usbfs > and it still handles the same functions as it used to. But it is part of > usbcore. > > You know, it's entirely possible that usbfs is the problem source. It's > not working quite right at the moment, and the person who has spent the > most time on fixing it is very busy with other things now. OK, given the limited "expertise" ressource that is available for fixing the problem, what could we do to figure? > > Is there an easy way to sniff USB traffic, an analogon to tcpdump might > > be helpful to see if there are differences in traffic? > > It would be nice if there were, but no one has written such a thing. I > could put together something quick that would work for 2.6. However, > you'd need to do it under both 2.4 and 2.6 to look for differences. Given that this machine has more than half a dozen USB ports on four UHCI hubs (plus an EHCI hub not counted against this), could one USB port be abused for sniffing the bus? I would buy or solder the necessary cable if it helps. > > 8096 ioctl(11, USBDEVFS_BULK, 0xbfffe220) = 4096 > > 8096 ioctl(11, USBDEVFS_BULK, 0xbfffe220) = 4096 > > 8096 ioctl(11, USBDEVFS_BULK > > Doesn't say too much beyond the fact that the program is working... What > happens if you do the same thing for the program that hangs? Or better That is the program that hangs. strace seems not to have printed the request varargs. Given the program got stuck unkillable (process state "D") in the ioctl, I'm not surprised. > yet, can you post both the strace output and the dmesg output for the same > run? Not on the list, too large. I can show the URL of a bzip2ed copy of the logs on some FTP/HTTP server once I've had the leisure to reboot the machine several times, and I can mail them off-list. -- Matthias Andree Encrypt your mail: my GnuPG key ID is 0x052E7D95 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
