> >> Thanks Paul. I just tried Fedora-Workstation-32-20200225.n.0.aarch64.raw.xz on my RPi4 but it behaves the same as I previously reported. There is a 5 minute pause after the eth0 link becomes ready and I then wind up in the dracut emergency shell. > > > > That's two different an unrelated problems. Is the pause with ethernet > > before the grub2 prompt? > > No - the pause is in the kernel. In an earlier email in this chain, I attached a file "session.log". Here is part of that file - note that the eth0 link comes up at around the 28 second mark. Then there is a 5 minute pause where nothing appears to be happening, and then at the 321 second mark, dracut starts printing timeout messages. I don't read attachments, much less compressed globs of information, sorry it takes too much time to search for a needle in a haystack. > [ 23.467681] raspberrypi-firmware soc:firmware: Request 0x00028001 returned status 0x00000000 > [ 23.969125] bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay) > [ 23.986485] bcmgenet fd580000.ethernet eth0: Link is Down > [ 27.394605] systemd-udevd (515) used greatest stack depth: 11696 bytes left > [ 28.172043] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx > [ 28.186922] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > [ 28.241941] NetworkManager (549) used greatest stack depth: 10272 bytes left > [ 234.092146] random: crng init done > [ 234.101385] random: 6 urandom warning(s) missed due to ratelimiting > [ 321.541094] dracut-initqueue[522]: Warning: dracut-initqueue timeout - starting timeout scripts > [ 322.921646] dracut-initqueue[522]: Warning: dracut-initqueue timeout - starting timeout scripts > > The "Warning: dracut-initqueue timeout" messages repeat for a quite a while, then at the 466 second mark we get the following: > > [ 464.979853] dracut-initqueue[522]: Warning: dracut-initqueue timeout - starting timeout scripts > [ 466.181960] dracut-initqueue[522]: Warning: dracut-initqueue timeout - starting timeout scripts > [ 466.183175] dracut-initqueue[522]: Warning: Could not boot. > Starting Setup Virtual Console... > [ OK ] Started Setup Virtual Console. > [ 466.475450] audit: type=1130 audit(1580894910.719:14): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > [ 466.475689] audit: type=1131 audit(1580894910.719:15): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > Starting Dracut Emergency Shell... > [ 466.661153] audit: type=1131 audit(1580894910.899:16): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > Warning: /dev/disk/by-uuid/369ee56a-5038-4040-b16e-f127f8a81ba0 does not exist What storage/medium are you booting off? Unless it's a network style of storage it's actually unlikely to be an issue here with the network side of things. More likely storage. Also what rev of the RPi4 hardware do you have? If it's one of the refresh versions there may be an issue around a firmware <-> kernel interaction. I should have a new rev 2Gb version in the next day or so, there's a proposed patch under review upstream but I think it might need a newer firmware as well. I'll be testing once I have all the pieces available. Peter _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
