Comment # 11 on bug 948369 from Oliver Neukum

(In reply to Bernhard Wiedemann from comment #6)
> (In reply to Peter Robertson from comment #3)
> > Created attachment 650815 [details]
> > USB device info
> > 
> > lsusb results in nothing, it just seems to stop and can't be killed or
> > backgrouded.
> > 
> > So instead find the entry from /proc/bus/input/devices.
> 
> lsusb not being able to be killed (not even with kill -9 ?)
> sounds strange and could point towards a kernel problem.

Yes, the xpad driver died in probe(). That means the device lock it held is
never released. lsusb must take forever in taking that lock. The taking is done
with mutex_lock(), which doesn't react to signals, hence the task is immortal.

lsusb is not to blame here. The xpad driver is to blame.