[fabien]

error: [drm: pid32623:intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A

doesn't seem to be the problem. After many reboot the mouse always froze as expected but this error doesn't show up any more in dmesg.

vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on wd0a (76e4ecc7f2cfaae0.a) swap on wd0b dump on wd0b
wskbd1: disconnecting from wsdisplay0
wskbd1 detached
ukbd0 detached
uhidev0 detached
uhid0 detached
uhid1 detached
uhid2 detached
wsmouse0 detached
ums0 detached
uhid3 detached
uhidev1 detached
uhid4 detached
uhid5 detached
uhid6 detached
uhid7 detached
uhidev2 detached
uhidev0 at uhub7 port 2 configuration 1 interface 0 "Microsoft Microsoft\M-. 2.4GHz Transceiver v8.0" rev 2.00/6.56 addr 2
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub7 port 2 configuration 1 interface 1 "Microsoft Microsoft\M-. 2.4GHz Transceiver v8.0" rev 2.00/6.56 addr 2
uhidev1: iclass 3/1, 28 report ids
uhid0 at uhidev1 reportid 18: input=0, output=0, feature=1
uhid1 at uhidev1 reportid 22: input=4, output=0, feature=0
uhid2 at uhidev1 reportid 23: input=0, output=0, feature=1
ums0 at uhidev1 reportid 26: 5 buttons, Z and W dir
wsmouse0 at ums0 mux 0
uhid3 at uhidev1 reportid 28: input=3, output=0, feature=0
uhidev2 at uhub7 port 2 configuration 1 interface 2 "Microsoft Microsoft\M-. 2.4GHz Transceiver v8.0" rev 2.00/6.56 addr 2
uhidev2: no report descriptor

Also, It happen with another mouse.

Looks like the USB port dies.
If I plug the mouse on a port in the front of the desktop, the problem keeps happening until the mouse is not working any more, like if the USB port is definitely dead.
If I plug the mouse on a port situated behind the desktop, the issue happen only once and then every is fine.

Why the port dies? Back to google...