This bug was fixed in the package initramfs-tools - 0.142ubuntu25.1
---
initramfs-tools (0.142ubuntu25.1) noble; urgency=medium
* configure_network: Call dhcpcd with --nolink --noipv4ll to succeed getting
a DHCP lease on the first try and avoid a 30 seconds delay (LP: #2065037)
I retried the failing armhf dep8 tests and they are now green.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called before interfaces have carrier causing a 29 seconds
This bug was fixed in the package initramfs-tools - 0.142ubuntu27
---
initramfs-tools (0.142ubuntu27) oracular; urgency=medium
* Run wrap-and-sort
* initramfs-tools-core: drop support for upgrading from < 0.138
* Convert debian/copyright to machine-readable format
* Switch to
Then I think it's OK (if you are satisfied me me being the only one
testing the fix) :).
Thanks again for your help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called
The ARP check is done to verify that the assigned IP address is not used
in the network. So using --noarp will skip this safety-check. IMO the
users should do such change explicitly if they want to trade safety by
speed (e.g. via a dhcpcd config setting that will be included in the
initrd).
--
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called
** Attachment added: "initramfs_proposed_testing.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5777133/+files/initramfs_proposed_testing.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "dmesg_proposed_testing.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5777132/+files/dmesg_proposed_testing.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Timo.
Sure, I just tested it and I get relatively good Results.
See my Conclusion below. Maybe some extra discussions needed about the
`--noarp` NOT being included in the patch, which causes the Boot time to
go from approx. 22s (with `--noarp`) to approx. 28s (without `-noarp`,
i.e. the
Hello Stefano, or anyone else affected,
Accepted initramfs-tools into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.142ubuntu25.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called before interfaces have carrier causing a 29 seconds
boot delay
To manage notifications about
** Description changed:
+ [ Impact ]
+
+ The boot time can be longer on system that configure their network in
+ the initrd.
+
+ [ Test Plan ]
+
+ The affected systems show "Sleeping $time seconds before retrying
+ getting a DHCP lease" in their boot log. Once applying the fix, this
+ message
Yes, here is the debdiff for the uploaded SRU fix.
** Patch added: "initramfs-tools_0.142ubuntu25.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776988/+files/initramfs-tools_0.142ubuntu25.1.debdiff
--
You received this bug notification
Yeah I can do that, that's lower-priority ish. The good thing is that it
works. If I cannot see what's happening, that's secondary, I can just
look at `dmesg` once the boot is completed, if I really wanted (or
`/run/initramfs/initramfs.debug`).
Will you write a Patch for this issue here, like you
For the black screen, can you open a separate bug report and document
what graphic card you use on that machine and what driver is used on the
running system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For the black screen, can you open a separate bug report and document
what graphic card you use on that machine and what driver is used on the
running system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "initramfs_v9_new_norap_main_workstation.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776545/+files/initramfs_v9_new_norap_main_workstation.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs,
So the good news is that the Fix can be replicated on 2 Machines now :).
ZFS Pool gets mounted at 19.679602 Seconds on the Main Workstation,
while it was getting mounted at 20.698236 Seconds on the Secondary
Laptop.
That's a bit surprising since the Main Workstation needs to unlock 2
Disks via
I had to reboot my Main Workstation due to some GTK/Mate/Desktop
Environment Issue (maybe related to NVIDIA Drivers ?).
Anyhow I took the opportunity to implement quickly the fixes we discussed:
- `/usr/lib/dhcpcd/dhcpcd-hooks/30-hostname`: `need_hostname || return 0`
-
Now I just tried with `dhclient` on my Main Workstation to check the
time it takes "from scratch" to bring up and get an IP from DHCP on
eno1.
Keep in mind that the "path" to the Router/Gateway (OPNSense Router:
192.168.1.7 master and 192.168.1.8 slave, or 192.168.1.1 Virtual IP) is
much longer
** Attachment added: "initramfs_v9_new_norap.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776538/+files/initramfs_v9_new_norap.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not sure how relevant it is, but **on a booted system**, if I call
`dhclient -v` the Interface gets automatically detected, up and offered
an IP by the DHCP Server in less than 5 seconds (probably even less than
3 seconds ...).
A bit better with `--no-arp` but not by much.
Output of
** Attachment added: "dmesg_v9_new_noarp.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776537/+files/dmesg_v9_new_noarp.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: initramfs-tools (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu)
21.67 - 4.42 = 17.25 for the dhcpcd call is quite long. So the remaining
initrd takes only 10 seconds.
dhcpcd claims the IP via ARP which takes some time. You can call dhcpcd
with `--noarp` to check how much time that takes. Besides of that dhcpcd
needs to bring up the interfaces and wait for
Yeah, I should have done that. I'm really getting tired and sleepy,
sorry about that.
The 28 seconds is the one we had before as well (the 27-28 s in ... v9,
wasn't it ?
But this error caused the script / function to behave similarly to v4 in
terms of timings. Could this indicate something else
** Attachment added: "initramfs_v9_new_b.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776402/+files/initramfs_v9_new_b.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You could comment out the complete if-condition instead of adding a
dummy variable. BTW, you can check the code with shellcheck after your
modification:
```
shellcheck -s sh -e SC3043,SC1090,SC1091
/usr/share/initramfs-tools/scripts/functions
```
Reducing the kernel+initrd time from 47 seconds
** Attachment added: "dmesg_v9_new_b.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776403/+files/dmesg_v9_new_b.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Maybe that was the issue indeed ...
Output of `systemd-analyze` after applying the beforementioned fix:
```
Startup finished in 28.780s (kernel) + 24.552s (userspace) = 53.333s
graphical.target reached after 24.517s in userspace.
```
--
You received this bug notification because you are a
Probably I had an error in the code, although no error was raised (or at least
I didn't catch it):
```
if [ -z "${DEVICE}" ]; then
# _set_available_devices_to_up
fi
```
An empty if-statement is not valid (at least in BASH it's not
Yes, FUNCNAME is only available in bash. You can echo some hard-coded
text, e.g.
```
configure_network() {
echo "$(cut -f1 -d' ' /proc/uptime) configure_network start"
[...]
echo "$(cut -f1 -d' ' /proc/uptime) configure_network end"
}
--
You received this bug notification because
The additional `wait_for_udev 10` is not needed (but it should not
consume any time at that place).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called before interfaces
About `cut -f1 -d' ' /proc/uptime` ... Wouldn't it be better to also
indicate where we are when that timestamp is registered ?
If it were BASH I'd probably do a echo "${FUNCNAME[0]} - $(cut -f1 -d' '
/proc/uptime)" but in busybox/dash I really do not know ...
--
You received this bug
Correct me if I'm wrong, but at one point you told me to ADD an `wait_for_udev
10` call before
(the now disabled) call to `_set_available_devices_to_up`.
Attached the latest `/usr/share/initramfs-tools/scripts/functions` just
to make sure we are on the same page with the Modifications.
**
dmesg_v9_new.debug has:
```
[ 47.337075] systemd[1]: Setting '/proc/sys/kernel/printk_devkmsg' to 'on'
```
That matches roughly 47.314s (kernel) from systemd-analyze. So no need
to redo v4_new.
v4_new shows 30 seconds of sleep and v9_new does not. Can you sprinkle
the code with `cut -f1 -d' '
v9_new output of `systemd-analyze`:
```
Startup finished in 47.314s (kernel) + 27.100s (userspace) = 1min 14.415s
graphical.target reached after 27.063s in userspace.
```
Do I need to repeat `v4_new` ? Looking at `dmesg` I don't see a need
since dmesg shows very similar results for v4_new and
** Attachment added: "initramfs_v9_new.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776399/+files/initramfs_v9_new.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg_v9_new.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776398/+files/dmesg_v9_new.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking at dmesg_v4_new.debug:
```
[ 47.841914] systemd[1]: Setting '/proc/sys/kernel/printk_devkmsg' to 'on'
```
This is the first log line from systemd after the initrd handed over the
control. So the initrd took roughly 48 seconds.
--
You received this bug notification because you are a
Can you run `systemd-analyse` after boot to get the boot time?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called before interfaces have carrier causing a 29 seconds
** Attachment added: "initramfs_v4_new.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776397/+files/initramfs_v4_new.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg_v4_new.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776396/+files/dmesg_v4_new.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Alright ...
So I issued:
- `apt-get install --reinstall initramfs-tools-core`
- `apt-get install --reinstall dhcpcd-base`
v4_new:
- applied `need_hostname || return 0` in
`/usr/lib/dhcpcd/dhcpcd-hooks/30-hostname`
- issued the usual `update-initramfs -k all -u; update-grub; update-initramfs
I suggest to restore the package versions by using `apt install
--reinstall` on those package. Then apply the changes that you mentioned
plus removing _set_available_devices_to_up in the v9 test. The IPv6
dhcpcd line is not relevant for our case since that code path is not
used in your case.
--
I think you deleted the _set_available_devices_to_up from the functions
file yourself when you wanted me to test a custom `functions` File.
I cannot find that function call (or function declaration for that
matter) anymore at least ...
I got a bit lost now though ...
So you want me to re-run:
You can use systemd-analyze to measure the boot speed. This should be
more reliable. For some data, it would be useful to boot three times and
average over the boot times (plus calculated deviation). The 5-6 seconds
difference is not plausible to me since v4 has a 29 seconds sleep. Could
you rerun
I cannot compare the timing at `initramfs_v9.debug` because I didn't
save `dmesg` output then.
I only have `dmesg_v4.debug` and `dmesg_v10.debug` / `dmesg_v11.debug`.
But you can argue that 5-6 seconds difference is not that big of a deal.
I could also re-run with v9 and save dmesg this time.
I opened bug #2065149 because I saw this failure in the logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called before interfaces have carrier causing a 29 seconds
The "-K --noipv4ll" is the solution. Looking at initramfs_v9.debug,
dhcpcd is only called once and you do not see any "Sleeping" log
messages.
initramfs_v10.debug takes longer because it calls dhcpcd twice. The
first call is killed due to "timed out". initramfs_v11.debug calls
dhcpcd three times.
** Attachment added: "initramfs_v11.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776176/+files/initramfs_v11.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And now another attempt with `for ROUNDTTT in 5 5 30 60 90 120; do`
(including also --noipv4ll).
Still approximatively 24 seconds, that seems to be the minimum thus far.
** Attachment added: "dmesg_v11.debug"
I did an attempt with `for ROUNDTTT in 5 15 30 60 90 120; do` (including
also --noipv4ll).
This brings it down from 30 seconds to approx. 24 seconds.
** Attachment added: "dmesg_v10.debug"
** Attachment added: "initramfs_v10.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776174/+files/initramfs_v10.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg_v9.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776171/+files/dmesg_v9.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'd say we went from 45 seconds until ZFS mounting to 30 seconds until
ZFS mounting with --noipv4ll (although I did NOT save all `dmesg` until
now, I am comparing the current `dmesg_v9.debug` with --noipv4ll against
`dmesg_v4.debug` that I had provided before at
** Attachment added: "initramfs_v9.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776172/+files/initramfs_v9.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In the first try it only gets a link local address, but no DHCP address.
Can you test calling dhcpcd with --noipv4ll?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called
OK I reverted as you instructed.
I then replaced the functions file with your version: `wget
https://launchpadlibrarian.net/728520148/functions -O
/usr/share/initramfs-tools/scripts/functions`
Followed by the usual:
`update-initramfs -k all -u; update-grub; update-initramfs -k all -u;
Here it is
** Attachment added: "initramfs_v8.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776089/+files/initramfs_v8.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That strange. dhcpcd gets the carrier now, but it still retries it.
Can you test the attached functions file? I changed some logging there.
BTW, you can revert the dhcpcd debugging, e.g. `sudo apt install
--reinstall dhcpcd-base` and then apply the `return 0` fix.
** Attachment added:
Here you have it
** Attachment added: "initramfs_v7.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776025/+files/initramfs_v7.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also the updated /usr/share/initramfs-tools/scripts/functions file since
it changed so much now ...
** Attachment added: "functions_v7.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776026/+files/functions_v7.debug
--
You received this bug
Can you test commenting out the call to _set_available_devices_to_up and
add "--nolink" as parameter to the dhcpcd call?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is
** Attachment added: "initramfs_v6b.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775933/+files/initramfs_v6b.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "initramfs_v6a.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775932/+files/initramfs_v6a.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sure. Here is the result. Before (v6a) and After (v6b) adding the
"wait_for_udev 10" call after the _set_available_devices_to_up call.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
Also the updated /usr/share/initramfs-tools/scripts/functions file since
it changed so much now ...
** Attachment added: "functions_v6b.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775934/+files/functions_v6b.debug
--
You received this bug
Thanks. Next iteration. Here is the updated logging function:
```
log_flags() {
echo "***"
for device in /sys/class/net/*; do
if [ ! -f "${device}/flags" ]; then
echo "*** ${device}/flags missing"
Here it's the result
** Attachment added: "initramfs_v5.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775867/+files/initramfs_v5.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you add following function to /usr/share/initramfs-
tools/scripts/functions:
```
log_flags() {
for device in /sys/class/net/*; do
echo "*** flags for $device";
if [ -f "${device}/flags" ]; then
cat "${device}/flags";
fi;
done
}
```
Please call this
** Package changed: dhcpcd (Ubuntu) => initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called before interfaces have carrier causing a 29 seconds
** Attachment added: "dmesg_v4.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775839/+files/dmesg_v4.debug
** Package changed: initramfs-tools (Ubuntu) => dhcpcd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
73 matches
Mail list logo
