Bug ID 1163771
Summary [RPI4] WLAN could stop running
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware aarch64
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-maintainers@forge.provo.novell.com
Reporter clin@suse.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

When the WLAN interface was enabled by WPA-PSK("home") via YaST, it was working
for a while and then it suddenly died afterward. This symptom still exists
although I have switched to different WLANs/SSIDs.

In this case, I downgraded the wpa_supplicant package from v2.9 to v2.6 because
somehow v2.9 can't work on ARM port images [pi2/3/4]

OS: OpenSUSE-Tumbleweed-20200201
Kernel: 5.4.14-1-default

Here are some kernel logs:
------------
[  391.274635] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[  707.177694] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 1023.290662] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 1339.201986] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 1655.322140] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 1971.328281] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 2287.341410] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 2603.251291] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 2919.261729] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 3235.275586] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 3551.287301] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 3867.297475] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready         
[ 4177.623093] ieee80211 phy0: brcmf_cfg80211_scan: Connecting: status (3)      
[ 4177.624656] ieee80211 phy0: brcmf_cfg80211_scan: Connecting: status (3)      
[ 4177.644403] ieee80211 phy0: brcmf_cfg80211_scan: Connecting: status (3)      
[ 4177.773375] ------------[ cut here ]------------                             
[ 4177.773501] WARNING: CPU: 0 PID: 5750 at net/wireless/sme.c:756
__cfg80211_connect_result+0x374/0x400 [cfg80211]
[ 4177.773505] Modules linked in: joydev af_packet iscsi_ibft iscsi_boot_sysfs
overlay br_netfilter bridge stp llc btsdio bluetooth ecdh_generic ecc xhci_pci
brcmfmac xhci_
hcd cpufreq_dt nls_iso8859_1 nls_cp437 brcmutil vfat fat cfg80211 rfkill
raspberrypi_cpufreq raspberrypi_hwmon crct10dif_ce bcm2835_wdt pcie_brcmstb
uio_pdrv_genirq leds_gp
io uio mmc_block dwc2 broadcom bcm_phy_lib udc_core usbcore mdio_bcm_unimac
sdhci_iproc sdhci_pltfm sdhci mmc_core clk_raspberrypi i2c_bcm2835
gpio_raspberrypi_exp bcm2835_
dma genet phy_generic gpio_regulator fixed sunrpc dm_mirror dm_region_hash
dm_log dm_mod sg efivarfs
[ 4177.773603] CPU: 0 PID: 5750 Comm: kworker/u8:0 Not tainted 5.4.14-1-default
#1 openSUSE Tumbleweed (unreleased)
[ 4177.773608] Hardware name: raspberrypi rpi/rpi, BIOS 2020.01 01/30/2020
[ 4177.773693] Workqueue: cfg80211 cfg80211_event_work [cfg80211]
[ 4177.773703] pstate: 60000005 (nZCv daif -PAN -UAO)
[ 4177.773784] pc : __cfg80211_connect_result+0x374/0x400 [cfg80211]
[ 4177.773864] lr : __cfg80211_connect_result+0x200/0x400 [cfg80211]
[ 4177.773868] sp : ffff8000106abcb0
[ 4177.773873] x29: ffff8000106abcb0 x28: 0000000000000000 
[ 4177.773882] x27: dead000000000100 x26: dead000000000122 
[ 4177.773889] x25: 0000000000000000 x24: ffff0000ee8e80e0 
[ 4177.773896] x23: ffff8000106abcf8 x22: ffff0000f69a9ec0 
[ 4177.773902] x21: ffff0000f0262000 x20: ffff0000ee8e8008 
[ 4177.773909] x19: ffff0000eac0a218 x18: 0000000000000000 
[ 4177.773915] x17: 0000000000000000 x16: ffffc86e83ef7e38 
[ 4177.773921] x15: 0000000000000000 x14: 00040f1004087f00 
[ 4177.773928] x13: 0000000000000000 x12: 0000000000000028 
[ 4177.773934] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f 
[ 4177.773941] x9 : fefefefefefefeff x8 : ffff0000f40d4044 
[ 4177.773947] x7 : 0000000000000000 x6 : ffff0000f44a00f8 
[ 4177.773953] x5 : ffff8000106abbc0 x4 : 0000000000000001 
[ 4177.773960] x3 : ffffc86e1dc2a9a0 x2 : 0000000000000000 
[ 4177.773966] x1 : 0000000000000000 x0 : 0000000000000000 
[ 4177.773973] Call trace:
[ 4177.774053]  __cfg80211_connect_result+0x374/0x400 [cfg80211]
[ 4177.774131]  cfg80211_process_wdev_events+0x1dc/0x2b8 [cfg80211]
[ 4177.774208]  cfg80211_process_rdev_events+0x40/0x98 [cfg80211]
[ 4177.774286]  cfg80211_event_work+0x24/0x38 [cfg80211]
[ 4177.774300]  process_one_work+0x1d0/0x468
[ 4177.774307]  worker_thread+0x150/0x4f0
[ 4177.774317]  kthread+0xec/0x118
[ 4177.774326]  ret_from_fork+0x10/0x18
[ 4177.774331] ---[ end trace 4be4a82a659b2a9e ]---


You are receiving this mail because: