[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 #9 from Alan Stern (stern@rowland.harvard.edu) ---
I don't understand exactly what the two logs in comments #5 and #6 are meant to
show.

Is the #5 log just the initial portion of the #6 log?  It looks that way.  You
really don't need to post two copies of the same information.

Also, when I asked for the dmesg log, I meant the output from the "dmesg"
command.  Not the output from journalctl.

As far as the logs indicate, the Sharkoon mouse was working correctly the whole
time.  It was detected during boot, and then about 4 minutes later you
unplugged it, plugged it back into the same port, and it was detected properly
again.

Your bug report says that the Sharkoon mouse is not recognized/detected with
the new memset implementation, but the logs show that it is.  Do you have any
logs of a boot where the mouse was not detected?

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

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