Our ACID box crashed this evening; could not ssh into it, and green lights on URIs not blinking. Rebooted after front panel shutdown, and the URI on node 27178 blinked real slow, and audio out of the radio was marginally there and choppy. Performed this twice with the same results then rebooted via ssh. The repeater is acting normal now, but I'm wondering what might be happening, and looking to not have a repeat performance. Below are the last few messages recorded after reboot. This pattern was the same for all three reboots. Here are my questions. Why would chan_usbradio.c assign USB device 4-1 (nothing there) to usb27179? Is the "possibly stuck USB read channel" a timing test? This seemed to pass shortly after. The stuck channel was the one that was blinking slowly and not responding properly to the radio. Thanks, Bob kk6ecm [Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater Init 27178 [Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater Init 27179 [Oct 28 18:51:46] NOTICE[2839] chan_usbradio.c: Assigned USB device 4-1 to usbradio channel usb27179 [Oct 28 18:51:46] WARNING[2838] chan_usbradio.c: Loaded parameters from usbradio_tune_usb27178.conf for device usb27178 . [Oct 28 18:51:46] WARNING[2839] chan_usbradio.c: Loaded parameters from usbradio_tune_usb27179.conf for device usb27179 . [Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Possibly stuck USB read channel. [usb27178] [Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Nope, USB read channel [usb27178] wasn't stuck after all.