[Redpine] HCI command timeout after resume from S4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
High
|
Shrirang Bagul | ||
linux-oem (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Redpine BT stops working after resume from S4.
Symptoms:
- The device list is increasing after resume.
- Error after command "hciconfig -a" which as:
Can't read local name on hci0: Connection timed out (110)
The reproduce steps:
1) Go to hibernate mode
$ sudo systemctl hibernate
2) Wakeup system by power recycle
3) Check the bluetooth list
$ hciconfig -a
hci1: Type: Primary Bus: SDIO
BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:0 acl:0 sco:0 commands:30 errors:0
Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
Link policy: RSWITCH
Link mode: SLAVE ACCEPT
hci0: Type: Primary Bus: SDIO
BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
UP RUNNING
RX bytes:1238 acl:0 sco:0 events:75 errors:0
TX bytes:0 acl:0 sco:0 commands:75 errors:0
Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
Link policy: RSWITCH
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)
4) Go to hibernate and wake again(as step 1-2)
5) Try ifconfig command to check wifi device
Result: command no response
This bug is for tracking purposes only, please don't triage.
Changed in linux-oem (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Critical |
tags: | added: originate-from-1771268 plano |
Changed in linux-oem (Ubuntu): | |
importance: | Critical → High |
importance: | High → Critical |
Changed in hwe-next: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
importance: | Critical → High |
assignee: | nobody → Shrirang Bagul (shrirang-bagul) |
Changed in linux-oem (Ubuntu Bionic): | |
status: | New → Fix Committed |
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Changed in linux-oem (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in hwe-next: | |
status: | Confirmed → Fix Released |
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- bionic' to 'verification- done-bionic' . If the problem still exists, change the tag 'verification- needed- bionic' to 'verification- failed- bionic' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!