On 13 October 2011 11:12, Greg KH <gregkh@xxxxxxx> wrote: > On Thu, Oct 13, 2011 at 10:31:08AM +1100, Aras Vaichas wrote: >> On 8 September 2010 10:34, Greg KH <gregkh@xxxxxxx> wrote: > > You are responding to a message from over a year ago? Yes, sorry, but it's the latest record I could find of this particular bug and talk of the patch. I just wanted to see if it was followed up or maybe there was some other issue that meant it couldn't be applied. >> Did this patch get applied and the problem resolved? > > Probably, I'd suggest you take a look at the kernel sources to verify > this, I can't remember what was applied last week very well, let alone > last year. Sorry, I should have checked there first. It doesn't appear to have been applied to the version I use on my product which is 2.6.33.7-at91-rt29. The patch appears to have been applied to 3.1-rc4 so it happened somewhere in between. Oh well, I guess I was unlucky. Luckily this is only affecting 1 customer that I know of. Our previous kernel bug was the JFFS2 garbage collection bug - that one was bricking our products in the field randomly on every power cycle. I built a solid-state power-cycle jig that switches our product on and off every few minutes to expose these types of problems. :) >> I'm running 2.6.33.7-rt29 and we have a customer in India who >> complains that they can't connect via USB. We don't have the problem >> here, or anywhere else that we know of. >> >> I looked at the logs of the device and it appears to have the same >> Oops error as the one that this patch addresses. > > What kernel version are they using? Hopefully something newer than the > date of this original email :) They are using our product, which is 2.6.33.7-at91-rt29. Aras -- 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
