** Description changed:
System cannot be waked by wowlan, but sometimes works.
When the wowlan not works and system waked by other wakeup sources, after
resume the wifi and BT would not functioning until reload driver.
The driver/FW info:
[ 395.217187] ven_rsi_91x: ================ RSI Version Info ==============
[ 395.217188] ven_rsi_91x: ================================================
[ 395.217192] ven_rsi_91x: FW Version : 1.5.4
[ 395.217198] ven_rsi_91x: Driver Version : RS9113.NB0.NL.GNU.LNX.1.2
[ 395.217200] ven_rsi_91x: Operating mode : 13 [Wi-Fi STA + BT DUAL]
[ 395.217201] ven_rsi_91x: Firmware file : RS9113_WLAN_BT_DUAL_MODE.rps
[ 395.217202] ven_rsi_91x: ================================================
Kernel version: 4.4.0-98-generic
Kernel snap: caracalla-kernel version:4.4.0-98.121-1 revision:58
BIOS version: 01.00.05 (Also tested with 01.00.03)
Tested SKU: T, Media, GPA
The reproduce steps:
1. Enable Wowlan and Wol in BIOS
2. Boot up Ubuntu core
3. Connect to Wifi AP
- $ nmcli d wifi connect <my ssid> password <my password>
+ $ nmcli d wifi connect <my ssid> password <my password>
4. Enable wowlan
- $ sudo iw phy phy0 wowlan enable magic-packet
+ $ sudo iw phy phy0 wowlan enable magic-packet
5. Enter suspend or hibernate
- $ sudo systemctl suspend
- or
- $ sudo systemctl hibernate
+ $ sudo systemctl suspend
+ or
+ $ sudo systemctl hibernate
6. Send wake signal from another machine
- # wakeonlan <Wifi MAC>
- or
- # sudo etherwake <Wifi MAC>
+ # wakeonlan <Wifi MAC>
+ or
+ # sudo etherwake <Wifi MAC>
7. If system not waked, try to wol or other wake source
- # wakeonlan <Ethernet MAC>
+ # wakeonlan <Ethernet MAC>
8. After resume, check the wifi/BT function, but not functioning.
- $ nmcli dev
- DEVICE TYPE STATE CONNECTION
- eth0 ethernet connected Wired connection 1
- wlan0 wifi disconnected --
- eth1 ethernet unavailable --
- cdc-wdm0 gsm unavailable --
- lo loopback unmanaged --
- $ nmcli dev wifi rescan
- $ nmcli dev wfii list
- No wifi APs found
+ $ nmcli dev
+ DEVICE TYPE STATE CONNECTION
+ eth0 ethernet connected Wired connection 1
+ wlan0 wifi disconnected --
+ eth1 ethernet unavailable --
+ cdc-wdm0 gsm unavailable --
+ lo loopback unmanaged --
+ $ nmcli dev wifi rescan
+ $ nmcli dev wfii list
+ No wifi APs found
- $ sudo bluetoothctl
- [NEW] Controller 00:23:A7:EA:65:64 0225399 [default]
- [bluetooth]# power on
- Failed to set power on: org.bluez.Error.Failed
+ $ sudo bluetoothctl
+ [NEW] Controller 00:23:A7:EA:65:64 0225399 [default]
+ [bluetooth]# power on
+ Failed to set power on: org.bluez.Error.Failed
The not functioning issue can be fixed by reload driver.
Also hibernate wakeup fails, and wake by other wake source. The Wifi/BT still
functioning which could be the FW is reloaded by driver.
+
+ This bug is only for tracking purporse, please do not triage.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Summary changed:
- Wifi/BT not functioning after s3 resume
+ Redpine: Wifi/BT not functioning after s3 resume
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742090
Title:
Redpine: Wifi/BT not functioning after s3 resume
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742090/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
