On Fri, 4 May 2007, Chris Rankin wrote: > --- Tejun Heo <[EMAIL PROTECTED]> wrote: > > How much hammering does it usually take? > > Typically, I sit at the keyboard for between 5 and 10 minutes starting and > exiting winecfg over > and over again. Opening the "Audio" tab sometimes (but not always) helps. > Once, I was "lucky" > enough to see the problem at boot-up too. But not seeing anything after 10 > minutes proves nothing, > as I observed with the 2.6.20.10 kernel. The only reason I kept at it with > that kernel was because > I was certain that nothing between 2.6.20.7 and 2.6.20.10 could have made the > slightest > difference. In fact, I was on the verge of downgrading to an earlier version > of "wine" before the > kernel finally consented to oops.
When the crash does occur, does it always involve the same sysfs file (or at least, the same endpoint number for the same device)? If it does, we could set up a pointer to the data structure every time it gets created. During the release routine we could see if the structure had been modified. We might even be able to find the code that is modifying it, which would indicate where the bug was. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
