On Mon, 21 Jan 2008 10:23:48 -0800 (PST) [EMAIL PROTECTED] wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=9790 > > Summary: strange USB related problem > Product: Drivers > Version: 2.5 > KernelVersion: 2.6.23 and above > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: USB > AssignedTo: [EMAIL PROTECTED] > ReportedBy: [EMAIL PROTECTED] > > > Latest working kernel version: 2.6.22.12 > > Earliest failing kernel version: 2.6.23.9
Regression... > Distribution: Gentoo > > Hardware Environment: > > ... > > Problem Description: > > First of all, I am sorry for the stupid bug title. Perhaps, you can suggest > Bus > the better one :). > > I use Nikon Coolscan V film scanner to scan the negative films. > > 002 Device 005: ID 04b8:0110 Seiko Epson Corp. Perfection 1650 > > The software is Vuescan (http://www.hamrick.com). This is closed source, > commercial product. I need this since I need infrared cleaning :(. This > software > uses libusb library to access the scanner. > > So, after upgrade from 2.6.20 to 2.6.23 the strange things become occur. > After scanning approx 30-35 frames (one frame is approximately 150Mb of data) > vuescan freezes (precisely, it goes into interruptible sleep). This can > happen > while scanning, and also is can happen while image processing (when the > software > does not talk with the scanner). Strace shows that the last system call is > msync(..,MS_ASYNC). After that another processes marked as 'D' appear, and > after some time the system becomes unresponsible. To prevent, it is possible > kill X server. After that there are no processes marked as 'D' and the system > seems to be absolutely normal. But, it is not the case. After some time > 'D'-processes begin to appear again and the system become more or less > unresponsible. So the system becomes completely broken and I need to reboot. I > compiled the kernel with all possible debug options, but this error is not > accompanies by any kernel message :(. With 2.6.23 this is absolutely > reproducible result. But to reproduce I need approx 2 hours (this is scanning > time) :( > > I also have tested 2.6.22 and 2.6.24. > > 2.6.22 seems to be not broken. > With 2.6.24-rc8 the situation becomes worse: the system completely freezes > after several scans. When things are stuck in D state, please hit ALT-SYSRQ-W or type "echo w > /proc/sysrq-trigger" and then send us (via reply-to-all to this email) the resulting dmesg output, thanks. - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
