> On Mon, Jan 28, 2019 at 5:18 PM Patrick Charles François Ernzer > <pcfe(a)redhat.com> wrote: > > There's some discussion of this on the upstream USB mailing list: > https://www.spinics.net/lists/linux-usb/msg176210.html > > I think this is also related: > https://www.spinics.net/lists/linux-usb/msg176223.html Yes. While I can live with adding 'xhci-plat-hcd', another annoyance is that on some of the reboots the bard boots fine but fails to initialise the network device: Bus 006 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter dmesg in that state at https://paste.fedoraproject.org/paste/zOqTsC8EiWsRaM2DTQojJA lsusb in that state at https://paste.fedoraproject.org/paste/Iq-ZBtl29GG9xvtVD2~Ijw I'm happy to provide more logs is needed, I've just wired up 2 serial consoles permanently, that makes life easier. FWIW: when the ODROID is in this state of not having access to the network, clean reboots issued via serial console end up in the same disconnected state. (I've tried 3 consecutive reboots just now). Additionally, I have the hardware watchdog set up and when I forcefully crash a system in this state with [root@localhost ~]# echo '1' > /proc/sys/kernel/sysrq [root@localhost ~]# echo 'c' > /proc/sysrq-trigger Network remains unreachable after the reboot triggered by the watchdog (also tested 3 times in a row) Power cycling the ODOID has, so far, always resolved the issue. pcfe _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
