Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1021805
| From | Forest <forestix@sonic.net> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#968519: dropbear-initramfs: race condition prevents launch at boot |
| Date | 2020-08-16 21:40 +0200 |
| Message-ID | <AEwFz-87s-3@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Package: dropbear-initramfs Version: 2020.80-1 Severity: important Dear Maintainer, About four times out of five, dropbear fails to launch at boot on the RockPro64 single-board computer. When it fails, I see this message repeated several times, scattered between various other messages on the serial console: ipconfig: no devices to configure Finally, this message appears: /scripts/init-premount/dropbear: .: line 279: can't open '/run/net-*.conf': No such file or directory The system then proceeds to the luks unlock prompt at the serial console only, with dropbear not running, so the boot process will not continue unless I connect a serial console and enter the password that way. I have tried adding all my ethernet-related driver modules to /etc/initramfs-tools/modules and rebuilding initramfs, but it didn't help. I have tried using ip= kernel command line arguments for a static address instead of DHCP, but that didn't help either. However, editing /usr/share/initramfs-tools/scripts/init-premount/dropbear does get it working. Making that script wait for a /run/net-*.conf file to appear before it calls configure_networking appears to be a solution. Even just sleeping for a few seconds before the configure_networking call seems to work, though I don't know how consistently. Based on this workaround and the fact that the aforementioned error messages are interleaved with other boot messages, it looks to me like dropbear's init-premount script is being run in parallel with driver and network setup, and often executing before the rk3399's onboard ethernet has a chance to finish initializing. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.7.0-2-arm64 (SMP w/6 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dropbear-initramfs depends on: ii busybox 1:1.30.1-5 ii dropbear-bin 2020.80-1 ii initramfs-tools 0.137 ii udev 246-2 Versions of packages dropbear-initramfs recommends: ii cryptsetup-initramfs 2:2.3.3-1 dropbear-initramfs suggests no packages. -- Configuration Files: /etc/dropbear-initramfs/config changed: DROPBEAR_OPTIONS="-p 222" -- no debconf information
Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#968519: dropbear-initramfs: race condition prevents launch at boot Forest <forestix@sonic.net> - 2020-08-16 21:40 +0200
Bug#968519: dropbear-initramfs: race condition prevents launch at boot Guilhem Moulin <guilhem@debian.org> - 2020-08-16 23:20 +0200
Bug#968519: dropbear-initramfs: race condition prevents launch at boot Forest <forestix@sonic.net> - 2020-08-17 03:10 +0200
Bug#968519: dropbear-initramfs: race condition prevents launch at boot Guilhem Moulin <guilhem@debian.org> - 2020-08-17 10:50 +0200
Bug#968519: dropbear-initramfs: race condition prevents launch at boot Forest <forestix@sonic.net> - 2020-08-19 08:40 +0200
Bug#968519: dropbear-initramfs: race condition prevents launch at boot Guilhem Moulin <guilhem@debian.org> - 2020-08-19 14:30 +0200
Bug#968519: dropbear-initramfs: race condition prevents launch at boot Forest <forestix@sonic.net> - 2020-08-31 21:10 +0200
csiph-web