[Bug 220272] Latent race condition in USB code unveiled with optimized memset_64.S

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=220272

--- Comment #15 from Alan Stern (stern@rowland.harvard.edu) ---
At the moment there's no way to know where the real problem lies.  It could be
something wrong with your new memset code; it could be something wrong in the
USB drivers; it even could be something wrong with the mouse itself.

The only way to find out more is to record what happens when the mouse fails to
work.  But doing that requires you either to issue commands before the problem
starts (that is, while the system is booting -- which can't be done) or else to
use special (and expensive!) hardware to monitor the signals on the USB cable.

If you can come up with a way to cause a failure that involves plugging in the
mouse cable after the system is running, then we would have some hope.  But
otherwise I'm afraid there's not much to try, other than guessing at possible
solutions.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.