On Thu, 14 Mar 2019 18:16:32 +0000 Peter Robinson <pbrobinson@xxxxxxxxx> wrote: > > Just tested with Kernel 5.0.1-300.fc29.armv7hl, same problem, out > > of 3 reboots one did not manage to initialise network. > > So one of the patches I referenced above, "usb: dwc3: exynos: Fix > error handling of clk_prepare_enable" is in 5.0 and just landed in > 4.20.16, > the other problem is basically summarised in the following > post > > https://www.spinics.net/lists/linux-usb/msg177861.html > > But should be mitigatable with "rd.driver.pre=xhci-plat-hcd " Sadly not, I boot with rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd (because I want the 5000M mode). One thing to note, since my initial testing I've switched from the HK power bricks to HK's ODROID power cable wired to a single 12V/20A bench supply. https://blog.pcfe.net/hugo/posts/2019-03-05-odroid-hc2-ceph-cluster/#notes-on-my-psu-choice While I'm confident in the power setup up to the HK power cable itself and have measured voltage under load up to the power distributors, I have not measured yet on the PCB, my current voltmeter leads are a tad too. The HK power cable seems a wee bit too much on the thin side for my taste. If you want I can re-test 5.0.1-300.fc29.armv7hl with one of HK's power bricks. In case you want it, I've dumped the console log at https://blog.pcfe.net/tmp/ once as generated by conserver(8), and once after running through strings(1) as I found the control codes annoying when trying to view in a browser ;-) Until I lost network connectivity, I triggered the reboots by ssh-ing in. lines 0020 to 0220 is the shutdown of the first systemctl reboot via ssh lines 0221 to 1348 is the system coming up fine and going down after I triggered again a clean reboot lines 1349 to 2462 same again At line 2464 the boot where I had no network starts. At line 3174 of that boot I get the first Timeout while waiting for setup device command At line 3459 I trigger a clean reboot via serial lines 3487 to 4446 the system boots but again the USB network fails to init. lines 4464 to end is a boot triggerd via watchdog, not helping either. As before removing power fixed the issue. Anything else I can test for you? pcfe -- ------------------------ http://www.pcfe.net/ ------------------------ Patrick C. F. Ernzer | e-mail: pcfe@xxxxxxxx --go-and-make-your-own-disclaimer--+---------------------------------- Abstinence makes the church grow fondlers -- http://imgur.com/r/atheism/BSg7HsL _______________________________________________ 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
