On Mon, 2 Nov 2015, Michael Reutman wrote: > On Wed, Oct 28, 2015 at 10:48 AM, Alan Stern <st...@rowland.harvard.edu> > wrote: > > The patch below is meant to apply on top of the previous patch. It's a > > quick-and-dirty workaround which ought to prevent the problem from > > occurring. Let's see if it does. > > Unfortunately, I have some bad news. It appears that the last patch > just pushes the issue further on down in time. Ran the test fresh > today and usb got "stuck" in around 15 to 20 minutes. This has > definitely improved things from before where it took less than a > minute to get everything out of sorts, so maybe we are on the right > track?
Okay, I was afraid of that. I'll have something else for you to try in a few days; things are a little busy here right now. > I captured dmesg and async output as previous and have attached them below. > > Also, should I still be enabling usbfs_snoop and usbfs_snoop_max > still? I tried it with and without those enabled just to see if they > made a difference, but they appear to end in the same state in > approximately the same amount of time. At this point they don't really matter any more. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
