wireless does not work on boot on RPi 3s
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| systemd (Ubuntu) |
Critical
|
Balint Reczey | ||
| Focal |
Critical
|
Balint Reczey |
Bug Description
I've setup a wireless config in /etc/netplan/
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.2-1ubuntu2
ProcVersionSign
Uname: Linux 5.4.0-1006-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu21
Architecture: armhf
Date: Thu Apr 2 19:02:27 2020
Lspci:
Lsusb:
Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Dimitri John Ledkov: Pending requested 2020-04-21
-
Diff: 102 lines (+88/-0)2 files modifieddebian/patches/dhcp-Allow-setting-request-options-again.patch (+87/-0)
debian/patches/series (+1/-0)
Brian Murray (brian-murray) wrote : | #2 |
Dave Jones (waveform) wrote : | #3 |
Also tested under armhf and arm64 on Raspberry Pi models 3B, 3A+, and 3B+. Results are the same as for bdmurray's tests with armhf on the 3B above.
My initial suspicion was that this was related to the wifi chipset used on the 3B (the BCM43430) to the 4B (the BCM43455). However, given the 3A+ and 3B+ also use the BCM43455 (same as the 4B) it's definitely not that.
Given that the only error ("DHCP4 CLIENT: Failed to attach event...") occurred in systemd-networkd I attempted to downgrade from version 245.2 to 244.3 (the prior release on Ubuntu). This fixes the issue on the 3B and 3A+ under armhf and arm64 (I skipped checking the 3B+ for time at this point).
At this point I'm reasonably confident it's an issue in systemd introduced sometime between 244.3 and 245.2 - and that it may be timing sensitive given that the 4B (which is significantly faster than the 3, 3A+ or 3B+) doesn't show the same symptoms but shares a wifi chipset with the 3A+ and 3B+.
Changed in systemd (Ubuntu Focal): | |
milestone: | none → ubuntu-20.04 |
summary: |
- wireless does not work on boot + wireless does not work on boot on RPi 3s |
Dan Streetman (ddstreet) wrote : | #4 |
commits 08c588d18b1 and 1b43e246020
Balint Reczey (rbalint) wrote : | #5 |
@ddstreet thanks, I'll pick those for the next upload (merging upcoming 245.4-2)
Changed in systemd (Ubuntu Focal): | |
status: | New → In Progress |
Brian Murray (brian-murray) wrote : | #6 |
Well I'm seeing a different failure with the systemd from the PPA.
Apr 3 19:47:53 ubuntu systemd-
Apr 3 19:47:53 ubuntu systemd-
Apr 3 19:47:53 ubuntu systemd-
Apr 3 19:47:53 ubuntu systemd-
Apr 3 19:47:53 ubuntu systemd-
Apr 3 19:47:53 ubuntu systemd-
Apr 3 19:47:53 ubuntu systemd-
Apr 3 19:47:53 ubuntu systemd-
ubuntu@ubuntu:~$ apt-cache policy systemd
systemd:
Installed: 245.4-2~
Dave Jones (waveform) wrote : | #7 |
I can confirm the behaviour Brian's seeing on the Pi 3B on armhf and arm64 with systemd 245.4-2 from the PPA Balint mentioned (and the same error message which appears to be from a chunk of code slightly beyond where we were last time - so we're moving forward at least :).
As before, wifi is working fine on the Pi 4B under armhf and arm64. Interestingly however, the Pi 3B+ (which shares the wifi chip with the 4B but is only slighter faster than the 3B) now has working wifi under armhf, but not arm64 (same error as the 3B on arm64). I was slightly surprised at this, so I double checked it with a couple of reboots - same results each time.
Balint Reczey (rbalint) wrote : | #8 |
For the record the packages were from this repo:
https:/
I'm preparing a new systemd upload with other fixes and the two commits suggested by @ddstreet.
I'll try to reproduce the remaining issues seen in #6 and #7 locally after that and target fixing them in another upload.
Balint Reczey (rbalint) wrote : | #9 |
@brian-murray @waveform Thanks for the testing!
Launchpad Janitor (janitor) wrote : | #10 |
This bug was fixed in the package systemd - 245.4-2ubuntu1
---------------
systemd (245.4-2ubuntu1) focal; urgency=medium
[ Balint Reczey ]
* Merge to Ubuntu from Debian unstable
* Refresh patches
- Dropped changes:
* units: Don't mount tracefs in LXC.
- Remaining changes:
* Specify Ubuntu's Vcs-Git
File: debian/control
https:/
* Enable EFI/bootctl on armhf.
File: debian/control
https:/
* Recommend networkd-dispatcher
File: debian/control
https:/
* Add conflicts with upstart and systemd-shim
File: debian/control
https:/
* debian/control: strengthen dependencies.
File: debian/control
https:/
* debian/rules: Set -Duser-path instead of patching the source for the same result
File: debian/rules
https:/
* config: tpm-pcrindex=12, on Ubuntu only.
File: debian/rules
https:/
* Ubuntu/extra: ship dhclient-enter hook.
Files:
- debian/
- debian/rules
https:/
https:/
https:/
* udev-udeb: ship modprobe.d snippet to force scsi_mod.scan=sync in d-i.
Files:
- debian/
- debian/
https:/
* debian/
Files:
- debian/
https:/
* debian/
drop resolvconf.conf drop-in, resolved integration moved to resolvconf package.
* debian/
Files:
- debian/
- debian/gbp.conf
https:/
Changed in systemd (Ubuntu Focal): | |
status: | In Progress → Fix Released |
tags: | removed: rls-ff-incoming |
Balint Reczey (rbalint) wrote : | #11 |
Only some of the affected configurations are fixed.
Changed in systemd (Ubuntu Focal): | |
status: | Fix Released → Confirmed |
Balint Reczey (rbalint) wrote : | #12 |
I was able to reproduce the issue on RPI 2 B 1.1 with an USB wifi dongle, too.
Looking into the root cause.
Changed in systemd (Ubuntu Focal): | |
status: | Confirmed → In Progress |
assignee: | nobody → Balint Reczey (rbalint) |
Changed in systemd (Ubuntu Focal): | |
importance: | Undecided → High |
Balint Reczey (rbalint) wrote : | #13 |
A test build of systemd with the fix is building in:
https:/
Changed in systemd (Ubuntu Focal): | |
importance: | High → Critical |
Dave Jones (waveform) wrote : | #14 |
Confirmed test build in the PPA in comment 13 (245.4-4ubuntu3) fixes the issue on both archs (armhf and arm64) on the Pi 3B, 3A+, and 3B+ (re-tested 4B as well to ensure nothing broken, and it's still working).
tags: | added: id-5e864eb1a142ba01fba1ebaa |
Dan Watkins (oddbloke) wrote : | #15 |
How does this relate to bug 1870346?
Balint Reczey (rbalint) wrote : | #16 |
@daniel-thewatkins I used a config very similar to https:/
Changed in systemd (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Launchpad Janitor (janitor) wrote : | #17 |
This bug was fixed in the package systemd - 245.4-4ubuntu3
---------------
systemd (245.4-4ubuntu3) focal; urgency=medium
* dhcp: Allow setting request options again
link_
set multiple times. (LP: #1870410)
File: debian/
https:/
* Don't try calling NULL callback in bus_wait_
This fixes a crash most frequently occurring in the Unity session
(LP: #1870930)
File: debian/
https:/
-- Balint Reczey <email address hidden> Wed, 22 Apr 2020 11:04:26 +0200
Changed in systemd (Ubuntu Focal): | |
status: | Fix Committed → Fix Released |
From /var/log/syslog:
ubuntu@ubuntu:~$ grep wlan0 /var/log/syslog net/devices/ wlan0. NETDEV_ CHANGE) : wlan0: link becomes ready 1028]: wlan0: Trying to associate with SSID 'javelin7' 1028]: wlan0: Associated with 50:c7:bf:15:c0:93 1028]: wlan0: CTRL-EVENT- CONNECTED - Connection to 50:c7:bf:15:c0:93 completed [id=0 id_str=] 1028]: wlan0: CTRL-EVENT- SUBNET- STATUS- UPDATE status=0 networkd[ 1109]: wlan0: Gained IPv6LL networkd[ 1109]: wlan0: Link DOWN networkd[ 1109]: wlan0: Lost carrier networkd[ 1109]: wlan0: Link UP networkd[ 1109]: wlan0: Gained carrier networkd[ 1109]: wlan0: Connected WiFi access point: javelin7 (50:c7:bf:15:c0:93) networkd[ 1109]: wlan0: Re-configuring with /run/systemd/ network/ 10-netplan- wlan0.network networkd[ 1109]: wlan0: IPv6 successfully enabled networkd[ 1109]: wlan0: IPv6 successfully enabled networkd[ 1109]: wlan0: DHCP4 CLIENT: Failed to attach event: Device or resource busy networkd[ 1109]: wlan0: Failed networkd- wait-online[ 1110]: managing: wlan0 networkd- wait-online[ 1110]: managing: wlan0 networkd- wait-online[ 1110]: managing: wlan0 networkd- wait-online[ 1110]: managing: wlan0
Apr 2 14:18:19 ubuntu systemd[1]: Found device /sys/subsystem/
Apr 2 14:18:19 ubuntu systemd[1]: Started WPA supplicant for netplan wlan0.
Apr 2 14:18:19 ubuntu kernel: [ 22.355445] IPv6: ADDRCONF(
Apr 2 14:18:19 ubuntu wpa_supplicant[
Apr 2 14:18:19 ubuntu wpa_supplicant[
Apr 2 14:18:19 ubuntu wpa_supplicant[
Apr 2 14:18:19 ubuntu wpa_supplicant[
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-
Apr 2 14:18:19 ubuntu systemd-