Please see attached var log messages.

Will update the feedback report link once available.

Something is wrong with this platform's USB controller or USB signalling.  I've measured roughly 1 failure in 10,000 link up/down cycles several different RTL8153 based USB GigE adapters (Anker, monoprice, linksys on newer kernels). This is no where close to that. This is more likely a problem with the USB Host controller.

I see three syptoms in 19 reboots with (2) and (3) being similar (but not the same):
1) "2018-10-22T13:03:11.311972-07:00 INFO kernel: [    1.157800] usb-storage 2-5:1.0: USB Mass Storage device detected"
   
2) 2018-10-22T12:58:58.441735-07:00 WARNING kernel: [    1.156360] usb 2-5: Device not responding to setup address.
   2018-10-22T12:58:58.441738-07:00 WARNING kernel: [    1.360339] usb 2-5: Device not responding to setup address.
   2018-10-22T12:58:58.441743-07:00 ERR kernel: [    1.560742] usb 2-5: device not accepting address 2, error -71
   2018-10-22T12:58:58.441744-07:00 ERR kernel: [    1.574734] i2c_designware i2c_designware.5: controller timed out

3) 2018-10-22T13:06:23.797408-07:00 INFO kernel: [   28.444907] r8152 2-5:1.0 eth0: Stop submitting intr, status -71
   2018-10-22T13:06:24.506233-07:00 ERR dhcpcd[1350]: eth0: dhcp if_readrawpacket: Network is down
   2018-10-22T13:06:24.506802-07:00 WARNING kernel: [   29.150930] xhci_hcd 0000:00:15.0: Cannot set link state.
   2018-10-22T13:06:24.506856-07:00 ERR kernel: [   29.150966] usb usb2-port5: cannot disable (err = -32)
   2018-10-22T13:06:24.506861-07:00 INFO kernel: [   29.150980] usb 2-5: USB disconnect, device number 2
   2018-10-22T13:06:24.506701-07:00 INFO avahi-daemon[1549]: Interface eth0.IPv4 no longer relevant for mDNS.
   2018-10-22T13:06:24.506741-07:00 INFO avahi-daemon[1549]: Leaving mDNS multicast group on interface eth0.IPv4 with address 100.90.35.226.
   2018-10-22T13:06:24.512252-07:00 ERR dhcpcd[1350]: dhcp_open: eth0: No such device
   2018-10-22T13:06:24.516155-07:00 INFO avahi-daemon[1549]: Withdrawing address record for 100.90.35.226 on eth0.


   In the first case the device came up as USB storage (look for "Storage" in messages) and the system (thank you mist!) recovered from that at the cost of ~10 seconds longer to bring up a link. We should see this no more than 1 in 1000 reboots.

(2) and (3) the device didn't accept the host controller's assignment of a bus address.(2) and (3) are slightly different with (3) being interesting in that the failure happened well after discovering and initialization of the device. (2) has happened before. But not at this high of a rate - again, maybe 1 in a few thousand (sorr, I don't have an exact number here).

BTW, this is a coral (unibuild) platform. How can I tell from the messages that this is a "Rabbid" device?

Which model of Monoprice adapter is being used?
If the Monoprice Adapter is USB type-A connector, which USBA-C adapter is used?

Its the monoprice adapter from techstop vending cabinet.

Yes it is Model: Rabbid, Board : Coral.

It is a USB Type-A connector, connected to USB port of the device. I did not use any USBA-C adapter.

Feedback report@
https://listnr.corp.google.com/report/85738672382