FS#74042 - QCA6390 fails to suspend

Attached to Project: Arch Linux
Opened by Kai (halan) - Sunday, 06 March 2022, 19:01 GMT
Last edited by Toolybird (Toolybird) - Thursday, 14 September 2023, 06:51 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
On my Dell XPS I cannot seem to suspend due to the wifi/bluetooth drivers. I tried both deep sleep and regular s2idle.

In dmesg I see this with the last line repeated over an over.
```
Mar 06 10:30:47 kai-xps kernel: hci_uart_qca serial0-0: failed to acquire enable gpio
Mar 06 07:52:23 kai-xps kernel: hci_uart_qca serial0-0: PM: failed to suspend: error -110
Mar 06 07:52:00 kai-xps kernel: hci_uart_qca serial0-0: PM: failed to suspend: error -110
Mar 06 07:51:48 kai-xps kernel: hci_uart_qca serial0-0: PM: failed to suspend: error -110
Mar 06 07:51:24 kai-xps kernel: hci_uart_qca serial0-0: PM: failed to suspend: error -110
```

There are some older reports on the Wiki that this can happen. Weirdly, I never encountered this before until switch from my old XPS to a replacement device of the same model.

I will try to set up a Windows dual boot once I have time to see if it is maybe a hardware issue, however this is a brand new device, so it seems unlikely.

Some more info:
lspci lists the device as follows and I am on the lastest kernel version (5.16.12-arch1-1)
`6c:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01)`
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 14 September 2023, 06:51 GMT
Reason for closing:  Upstream
Additional comments about closing:  Clearly not an Arch packaging issue. If still happening with latest kernels/pkgs, please report upstream and/or visit the proper support Arch support channels (Forum, etc)
Comment by Kai (halan) - Sunday, 06 March 2022, 22:07 GMT
Also, not sure if this is related but after some time running my system bluetooth stops working. I see the following error in the logs.

```
Mar 06 15:38:16 kai-xps kernel: audit: type=1334 audit(1646602696.498:225): prog-id=0 op=UNLOAD
Mar 06 15:39:49 kai-xps kernel: Bluetooth: hci0: QCA collecting dump of size:458752
Mar 06 15:39:50 kai-xps kernel: Bluetooth: hci0: QCA memdump Done, received 458752, total 458752
Mar 06 15:39:50 kai-xps kernel: Bluetooth: hci0: mem_dump_status: 1
Mar 06 15:39:50 kai-xps kernel: Bluetooth: hci0: waiting for dump to complete
```
Comment by Kai (halan) - Sunday, 03 April 2022, 19:01 GMT
On linux 5.17 and bluez 5.64 the error now is slightly different.

```
[ 6295.536577] Bluetooth: hci0: ACL packet for unknown connection handle 2
[ 6295.549319] Bluetooth: hci0: ACL packet for unknown connection handle 2
[ 6295.551728] Bluetooth: hci0: ACL packet for unknown connection handle 2
[ 9134.562283] Bluetooth: hci0: QCA collecting dump of size:458752
[ 9142.768629] Bluetooth: hci0: Injecting HCI hardware error event
[ 9142.768643] Bluetooth: hci0: mem_dump_status: 3
[ 9142.768645] Bluetooth: hci0: clearing allocated memory due to memdump timeout
[ 9165.594844] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 9165.594856] Bluetooth: hci0: mem_dump_status: 3
[ 9165.594857] Bluetooth: hci0: clearing allocated memory due to memdump timeout
[ 9167.728139] Bluetooth: hci0: Opcode 0x c03 failed: -110
```

I also did set up dual boot with windows and was not able to reproduce the issue there.
Comment by Kai (halan) - Wednesday, 27 April 2022, 06:47 GMT
Some more info. Manually removing and re-adding the hci_uart does not fix the issue either.

```
[14880.415011] Bluetooth: HCI UART driver ver 2.3
[14880.415015] Bluetooth: HCI UART protocol H4 registered
[14880.415016] Bluetooth: HCI UART protocol BCSP registered
[14880.415040] Bluetooth: HCI UART protocol LL registered
[14880.415041] Bluetooth: HCI UART protocol ATH3K registered
[14880.415049] Bluetooth: HCI UART protocol Three-wire (H5) registered
[14880.415086] Bluetooth: HCI UART protocol Intel registered
[14880.415126] Bluetooth: HCI UART protocol Broadcom registered
[14880.415134] Bluetooth: HCI UART protocol QCA registered
[14880.415135] Bluetooth: HCI UART protocol AG6XX registered
[14880.415141] Bluetooth: HCI UART protocol Marvell registered
[14880.415459] hci_uart_qca serial0-0: failed to acquire enable gpio
[14880.415756] Bluetooth: hci0: setting up ROME/QCA6390
[14882.772367] Bluetooth: hci0: command 0xfc00 tx timeout
[14890.878949] Bluetooth: hci0: Reading QCA version information failed (-110)
[14890.878965] Bluetooth: hci0: Retry BT power ON:0
[14893.225599] Bluetooth: hci0: command 0xfc00 tx timeout
[14901.332188] Bluetooth: hci0: Reading QCA version information failed (-110)
[14901.332204] Bluetooth: hci0: Retry BT power ON:1
[14903.682056] Bluetooth: hci0: command 0xfc00 tx timeout
[14911.785324] Bluetooth: hci0: Reading QCA version information failed (-110)
[14911.785344] Bluetooth: hci0: Retry BT power ON:2
[14914.132047] Bluetooth: hci0: command 0xfc00 tx timeout
[14922.241934] Bluetooth: hci0: Reading QCA version information failed (-110)

```

Loading...