On Fri, Jan 28, 2011 at 1:52 PM, Greg KH <greg@xxxxxxxxx> wrote: > You do realize how many changes have gone into the kernel since 2.6.29, > right? That's many years and tens of thousands of patches, so if you > are stuck with that one, you are really on your own (or you need to push > on your vendor to resolve this issue, it's their fault, not ours). Understood. The problem is hard to reproduce, so I was hoping that someone might see something in the stack traces that triggers a memory and they could point me at the fix. > If you can duplicate this on .37, we will be glad to help out here. Yup, working on it now. Thanks, Pete -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
