Am Donnerstag, 17. Juni 2010 11:33:17 schrieb Zoltan Gaal: > My question is that, what can be the cause of this EPERM (I could not > trace back the exact return position of this error due to the function > pointers in the driver specific codes) ? I've also tried to guard the > urb access using spin_lock_irqsave/spin_unlock_irqrestore without any > success. The usb_kill_urb is not called either (especially as the error > occurs sometimes after the arrival of the first packages) -EPERM means that usb_kill_urb() or usb_poison_urb() have been used. You might obtain a stack trace with WARN_ON(). IIRC 2.6.24 didn't have the poison primitives. Technically urb->reject is checked. HTH Oliver -- 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
