Potential Bug in WiFi Driver for Up Core in Ubuntu 16.04
I think I may have found a potential bug in the WiFi driver for Up Core in Ubuntu 16.04. I have experienced this and reproduced in 4 Up Cores I own.
We have our up cores running for 24hrs a day with a automatic reboot at 1am and a reboot if network connection drops out. After a day or two of use, a reboot causes the WiFi to fails to connect automatically and cannot connect manually. A single force reboot, multiple force reboots or a shutdown is required to fix the issue.
- Running Ubuntu 16.04
- SSID is hidden
- WiFi powersave mode is disabled
- Running openvpn
Syslog during boot that shows the firmware halting. We've compared it to a successful boot and the only difference are these lines which suggest its a firmware problem:
NetworkManager: <info> [1540562434.7168] device (wlan0): supplicant interface state: inactive -> scanning
kernel: [ 13.383586] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
kernel: [ 16.096305] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout wpa_supplicant: wlan0: Failed to initiate sched scan
I've attatched the extended syslog.
Kernal Log also shows this:
Oct 27 01:05:53 host-name kernel: [ 331.761018] brcmfmac: brcmf_run_escan: error (-110)
Oct 27 01:05:53 host-name kernel: [ 331.761048] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Has anyone else experienced this problem?
- 302 All Categories
- 104 Announcements & News
- 50 Product News - New Product/Product Change Notice/ End-of-life
- 184 Welcome Developers!
- 50 Unboxing & Project Sharing
- 24 Tech Updates
- 477 UP Products
- UP Element i12 Edge
- 1 UP Squared V2
- 2 UP 4000
- 23 UP Xtreme i11
- 30 UP Squared 6000
- 42 UP Squared Pro
- 137 UP Xtreme
- 806 UP Squared
- 1.4K UP Board
- 87 UP Core Plus
- 219 UP Core
- 3 UP Xtreme Lite
- 43 UP AI Edge
- 215 Starter Kits & Peripheral