Computer stops responding on resume from suspend

[Andrew Marshall]

Crash on resume from suspend. The following messages appear and the computer stops responding:

```
[ 26.227264] Bluetooth: hci0: Reading supported features failed (-16)
[ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask failed (-95)
```

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez (not installed)
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 4 22:50:23 2021
InstallationDate: Installed on 2021-09-16 (49 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)

[I-Cat (i-cat)]

uhh, wow The cpu info dont match and proc info.... let me look at the package. This looks more like a driver issue. I Have seen this before.

[I-Cat (i-cat)]

sudo apt install bluz
snap install bluz

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Andrew Marshall (algodynamic)]

Hi, apologies if bluez is not the appropriate package. I have followed the above instructions in an case.

1. No crash files present.

2. The following problems were reported on errors.ubuntu.com

https://errors.ubuntu.com/oops/feac943a-8847-11eb-9538-fa163ee63de6
https://errors.ubuntu.com/oops/7f383282-8841-11eb-9347-fa163e6cac46
https://errors.ubuntu.com/oops/414874ba-40fd-11e9-90bf-fa163e6cac46
https://errors.ubuntu.com/oops/6c93da58-3552-11e9-9eff-fa163e102db1

[Daniel van Vugt (vanvugt)]

Thanks but none of those crashes are related to BlueZ. And even if you did have a BlueZ crash it wouldn't cause the computer to stop responding.

If you can't find any more error reports like above then please:

1. Reproduce the bug again.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

[Andrew Marshall (algodynamic)]

Hi,

After the latest Ubuntu updates I am no longer experiencing this issue (possibly nvidia related?)

Thanks for your support.