Re: port-arm/55317

[mlelstv%serpens.de@localhost (Michael van Elst)]

The following reply was made to PR port-arm/55317; it has been noted by GNATS.

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-arm/55317
Date: Thu, 15 Dec 2022 09:32:42 -0000 (UTC)

 cryintothebluesky%gmail.com@localhost (Sad Clouds) writes:
 
 >Not tried recent -current yet, however this really needs fixing in the
 >stable release. The question is - why /etc/rc.d/network runs before
 >kernel manages to attach mue0 network interface? 
 
 USB is always "hot-plugging", the kernel doesn't know how long to wait
 for an USB device to attach.
 
 [     5.294732] uhub2: multiple transaction translators
 [     5.294732] uhub2: 3 ports with 2 removable, self powered
 [     5.634775] uhub0: autoconfiguration error: illegal enable change, port 1
 ...
 [     5.644779] boot device: ld0
 [     5.644779] root on ld0a dumps on ld0b
 [     5.664781] root file system type: ffs
 ...
 [     7.044973] mue0 at uhub2 port 1
 [     7.044973] mue0: SMSC (0x424) LAN7800 USB 3.1 gigabit ethernet device (0x7800), rev 2.10/3.00, addr 4
 [     7.335012] mue0: LAN7800 id 0x7800 rev 0x2
 
 two seconds later mue0 sees a carrier and
 nine seconds later dhcpcd gets an IP address.
 
 A static configuration might come too early. Best solution would be
 that the network script waits until the interfaces that it should
 configure have appeared. Basically s smarter version of the sleep
 that you added.
 
 We also need a configurable delay for the kernel itself to wait
 before trying to mount the root filesystem.