[syslog] vmunix: USB frame sequencing

FYI, this is nothing to concern.
This is not a critical messages. These messages are generated because of
frame sequence numbers being missed. These frame numbers are most likely
missed due to network collisions.

Collisions are not possible on a USB bus. The whole communication is strictly
controlled and initiated by the host bus controller. The host controller
generates a start of frame packet every one milli-second. The host controller
keeps track of the sequence numbers in a register (reset the driver internal
sequence numbers). The piece of code is there to allow us to detect when we
missed the USB interrupt for this sequence number register wrap around. It is
not clear why this interrupt was missed but the event itself is not considered