Random black screen when resuming from suspend with a Bluetooth device

antux18 · 2025-01-11 21:58:09

Fortunately, I saved this log (and rebooted using the SysRq keys (Ctrl+Alt+PrtScr+B))

seth · 2025-01-12 08:33:47

janv. 08 15:33:31 antoine-Inspiron-3650 /usr/lib/gdm-x-session[738]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=611ce624-0696-4fa2-8c3a-f637b7884d08 rw loglevel=3 quiet splash sysrq_always_enabled=1

janv. 08 15:33:27 antoine-Inspiron-3650 kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
janv. 08 15:33:27 antoine-Inspiron-3650 kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
janv. 08 15:33:27 antoine-Inspiron-3650 kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
janv. 08 15:33:31 antoine-Inspiron-3650 /usr/lib/gdm-x-session[738]: (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/simple-framebuffer.0/drm/card0
janv. 08 15:33:31 antoine-Inspiron-3650 NetworkManager[611]: <info>  [1736346811.2768] Config: added 'bgscan' value 'simple:30:-70:86400'
janv. 08 15:33:40 antoine-Inspiron-3650 /usr/lib/gdm-x-session[1486]: (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/simple-framebuffer.0/drm/card0
janv. 08 17:22:18 antoine-Inspiron-3650 NetworkManager[611]: <info>  [1736353338.3926] Config: added 'bgscan' value 'simple:30:-70:86400'

This is before the resume

janv. 08 15:33:40 antoine-Inspiron-3650 /usr/lib/gdm-x-session[1486]: (EE) NVIDIA(GPU-1): Failed to initialize the NVIDIA graphics device!

but - despite recently VRAM preservation failures w/ nvidia have shown up what should™ still allow you to ctrl+alt+f3 yourself out of this - we'll throw stuff at it:

nvidia_drm.modeset=1 nvidia_drm.fbdev=0 nvidia.NVreg_EnableGpuFirmware=0

Perhaps remove "splash" and "quiet" in case the splash thing is blocking the framebuffer and that's why you cannot switch the VT in this situation.

Wrt the BT situation

janv. 08 15:36:21 antoine-Inspiron-3650 kernel: Bluetooth: hci0: corrupted SCO packet
janv. 08 15:36:21 antoine-Inspiron-3650 kernel: Bluetooth: hci0: corrupted SCO packet

and after the resume

janv. 08 17:22:24 antoine-Inspiron-3650 bluetoothd[1007]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for xx:xx:xx:xx:xx:xx: Device or resource busy

antux18 · 2025-02-08 17:50:02

Hello,

As I said in message #24, I added both "usbcore.autosuspend=-1" and "modprobe.blacklist=ath3k" to the "GRUB_CMDLINE_LINUX_DEFAULT" string in /etc/default/grub, but I lost my Bluetooth adapter again today (it won't come back with "sudo modprobe ath3k && sudo rfkill unblock bluetooth").

I also added "nvidia_drm.modeset=1 nvidia_drm.fbdev=0 nvidia.NVreg_EnableGpuFirmware=0" and removed "quiet" and "splash" but I cannot tell if it was effective or not yet since the black screen bug didn't happen since (I'll try the "Ctrl+Alt+F3" trick if it happens again).

Wrt the BT situation
janv. 08 15:36:21 antoine-Inspiron-3650 kernel: Bluetooth: hci0: corrupted SCO packet
janv. 08 15:36:21 antoine-Inspiron-3650 kernel: Bluetooth: hci0: corrupted SCO packet
and after the resume
janv. 08 17:22:24 antoine-Inspiron-3650 bluetoothd[1007]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for xx:xx:xx:xx:xx:xx: Device or resource busy

I'm not sure what you mean by that...

PS : I'm only using this PC every two week-ends, hence the delay in my replies.

Last edited by antux18 (2025-02-08 17:53:46)

seth · 2025-02-08 21:19:11

Mostly recording where this is falling apart - this is from some headset? Is that your only BT device?

antux18 · 2025-02-09 00:03:19

Yes, it is a headset. I am sometimes using other BT devices, but this is currently the only one.

seth · 2025-02-09 08:01:14

You're sleeping deep (S3, not s2idle) so the BT controller will shut down, BT disconnects only after the wakeup (or rather fails at that)

janv. 08 17:22:17 antoine-Inspiron-3650 bluetoothd[1007]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
janv. 08 17:22:17 antoine-Inspiron-3650 kernel: done.
janv. 08 17:22:17 antoine-Inspiron-3650 kernel: random: crng reseeded on system resumption
janv. 08 17:22:17 antoine-Inspiron-3650 kernel: PM: suspend exit
janv. 08 17:22:17 antoine-Inspiron-3650 systemd[1]: Starting Load/Save RF Kill Switch Status...
janv. 08 17:22:17 antoine-Inspiron-3650 systemd-sleep[13195]: System returned from sleep operation 'suspend'.
janv. 08 17:22:17 antoine-Inspiron-3650 systemd[1]: systemd-suspend.service: Deactivated successfully.
janv. 08 17:22:17 antoine-Inspiron-3650 bluetoothd[1007]: Endpoint unregistered: sender=:1.88 path=/MediaEndpoint/A2DPSource/ldac
janv. 08 17:22:17 antoine-Inspiron-3650 bluetoothd[1007]: Endpoint unregistered: sender=:1.88 path=/MediaEndpoint/A2DPSink/aptx_hd

Try to rfkill/unkill bluetooth w/ a sleep hook, https://wiki.archlinux.org/title/Power_ … stem-sleep

But I doubt that's related to the black screen situation?

antux18 · 2025-02-09 14:57:21

seth wrote:

Try to rfkill/unkill bluetooth w/ a sleep hook, https://wiki.archlinux.org/title/Power_ … stem-sleep

Here is my sleep hook, but I don't know if it's the right way to do it (written to /usr/lib/systemd/system-sleep/bt-fix.sh with execution permission):

#!/bin/sh
case $1/$2 in
  pre/*)
    echo "Disabling Bluetooth..."
    sudo rfkill block bluetooth
    echo "Bluetooth disabled."
    ;;
  post/*)
    echo "Reenabling Bluetooth..."
    sudo rfkill unblock bluetooth
    echo "Bluetooth reenabled."
    ;;
esac

seth wrote:

But I doubt that's related to the black screen situation?

According to what you said : I guess no, it is rather related to GDM/Nvidia, even though the black screen usually happens when the system resumes from suspend and that a BT device was connected before suspending (so it might be related to BT as well? I'm confused...).

seth · 2025-02-09 19:12:37

The script runs a root, no need (nor good idea) to sudo anything.

We shall see whether either of the problems returns, but since you've also addressed the nvidia situation (which might be down to failing https://wiki.archlinux.org/title/NVIDIA … er_suspend - which is enabled by default but your RAM may be insufficient in comparism to its use and the amount of VRAM?) *iff* the both problems are gone you won't know what addressed what.

You might want to delay the BT mitigation and see whether you can get a BT failure w/o a GPU failure.

Arch Linux

#26 2025-01-11 21:58:09

Re: Random black screen when resuming from suspend with a Bluetooth device

#27 2025-01-12 08:33:47

Re: Random black screen when resuming from suspend with a Bluetooth device

#28 2025-02-08 17:50:02

Re: Random black screen when resuming from suspend with a Bluetooth device

#29 2025-02-08 21:19:11

Re: Random black screen when resuming from suspend with a Bluetooth device

#30 2025-02-09 00:03:19

Re: Random black screen when resuming from suspend with a Bluetooth device

#31 2025-02-09 08:01:14

Re: Random black screen when resuming from suspend with a Bluetooth device

#32 2025-02-09 14:57:21

Re: Random black screen when resuming from suspend with a Bluetooth device

#33 2025-02-09 19:12:37

Re: Random black screen when resuming from suspend with a Bluetooth device

Board footer