[SOLVED] X crash to mouse cursor black screen upon restoring from suspend--> COMRESET failed (errno=-16)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
X crash to mouse cursor black screen upon restoring from suspend--> COMRESET failed (errno=-16)
Hi all,
been struggling to fix a problem I have when my pc resumes from suspend. Almost every time it hangs to black screen with mouse pointer until I "ctrl-alt-backspace" to recover the X session login. I have tried so many things to no avail and am stumped. I don;t think it's a hardware issue, but instead related to the nvid drivers. I had a similar prob with an older GPU before I upgraded. On my older NV card I simply ran nouveau drivers and it went away. With this card nouveau does not work right, so I went with prop nv drivers from SBO kernel/driver/libxnvctrl, etc. Everything works fine aside from this issue. The ATA7/ATA8 drives throwing this error on restore are 2 SATA add-on drives. The boot drive is a nvme. Below is some basic system info and complete dmesg. I did a suspend and resume starting around second 79 followed by resume to show the COMRESET ERROR. This is when the screen hangs on black resuming. Thanks for any help. I have scoured around for info and know I am not the only one with this issue unresolved.
bash-5.2# dmesg I HAD TO DELETE ALOT OF THIS TO GET THE MSG LENGTH DOWN
[ 0.000000] Linux version 6.6.22 (root@z-mp.slackware.lan) (gcc (GCC) 13.2.0, GNU ld version 2.42-slack151) #1 SMP PREEMPT_DYNAMIC Fri Mar 15 15:52:16 CDT 2024
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-huge-6.6.22 root=UUID=a398f0bd-2c57-4782-8f06-86a777ad1fe7 ro
[ 0.000000] x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
[ 50.545634] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 50.658655] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 50.773662] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 50.893233] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 50.942035] Bluetooth: RFCOMM TTY layer initialized
[ 50.942041] Bluetooth: RFCOMM socket layer initialized
[ 50.942044] Bluetooth: RFCOMM ver 1.11
[ 51.003023] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 51.117181] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 77.535886] wlan0: deauthenticating from 5c:62:8b:44:e7:03 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 78.252388] PM: suspend entry (deep)
[ 78.253287] Filesystems sync: 0.000 seconds
[ 78.582300] Freezing user space processes
[ 78.583644] Freezing user space processes completed (elapsed 0.001 seconds)
[ 78.583647] OOM killer disabled.
[ 78.583648] Freezing remaining freezable tasks
[ 78.584740] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[ 78.584776] printk: Suspending console(s) (use no_console_suspend to debug)
[ 78.607777] sd 7:0:0:0: [sdb] Synchronizing SCSI cache
[ 78.610695] sd 6:0:0:0: [sda] Synchronizing SCSI cache
[ 78.611946] ata7.00: Entering standby power mode
[ 78.613678] ata8.00: Entering standby power mode
[ 79.097110] ACPI: PM: Preparing to enter system sleep state S3
[ 79.097506] ACPI: PM: Saving platform NVS memory
[ 79.097540] Disabling non-boot CPUs ...
[ 79.102643] smpboot: CPU 1 is now offline
[ 79.106200] smpboot: CPU 2 is now offline
[ 79.107706] smpboot: CPU 3 is now offline
[ 79.109063] smpboot: CPU 4 is now offline
[ 79.112138] smpboot: CPU 5 is now offline
[ 79.113509] smpboot: CPU 6 is now offline
[ 79.116571] smpboot: CPU 7 is now offline
[ 79.119544] smpboot: CPU 8 is now offline
[ 79.121002] smpboot: CPU 9 is now offline
[ 79.123946] smpboot: CPU 10 is now offline
[ 79.125459] smpboot: CPU 11 is now offline
[ 79.126761] smpboot: CPU 12 is now offline
[ 79.129649] smpboot: CPU 13 is now offline
[ 79.131030] smpboot: CPU 14 is now offline
[ 79.133877] smpboot: CPU 15 is now offline
[ 79.135238] smpboot: CPU 16 is now offline
[ 79.136679] smpboot: CPU 17 is now offline
[ 79.138110] smpboot: CPU 18 is now offline
[ 79.139624] smpboot: CPU 19 is now offline
[ 79.142201] ACPI: PM: Low-level resume complete
[ 79.142261] ACPI: PM: Restoring platform NVS memory
[ 79.143228] Enabling non-boot CPUs ...
[ 79.143252] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 79.146171] CPU1 is up
[ 79.146182] smpboot: Booting Node 0 Processor 2 APIC 0x8
[ 79.151694] CPU2 is up
[ 79.151703] smpboot: Booting Node 0 Processor 3 APIC 0x9
[ 79.154528] CPU3 is up
[ 79.154537] smpboot: Booting Node 0 Processor 4 APIC 0x10
[ 79.163835] CPU4 is up
[ 79.163844] smpboot: Booting Node 0 Processor 5 APIC 0x11
[ 79.166540] CPU5 is up
[ 79.166548] smpboot: Booting Node 0 Processor 6 APIC 0x18
[ 79.178029] CPU6 is up
[ 79.178037] smpboot: Booting Node 0 Processor 7 APIC 0x19
[ 79.180560] CPU7 is up
[ 79.180569] smpboot: Booting Node 0 Processor 8 APIC 0x20
[ 79.194231] CPU8 is up
[ 79.194239] smpboot: Booting Node 0 Processor 9 APIC 0x21
[ 79.197563] CPU9 is up
[ 79.197572] smpboot: Booting Node 0 Processor 10 APIC 0x28
[ 79.211382] CPU10 is up
[ 79.211391] smpboot: Booting Node 0 Processor 11 APIC 0x29
[ 79.214561] CPU11 is up
[ 79.214570] smpboot: Booting Node 0 Processor 12 APIC 0x30
[ 79.228444] CPU12 is up
[ 79.228453] smpboot: Booting Node 0 Processor 13 APIC 0x31
[ 79.231582] CPU13 is up
[ 79.231592] smpboot: Booting Node 0 Processor 14 APIC 0x38
[ 79.240604] CPU14 is up
[ 79.240613] smpboot: Booting Node 0 Processor 15 APIC 0x39
[ 79.243602] CPU15 is up
[ 79.243610] smpboot: Booting Node 0 Processor 16 APIC 0x48
[ 79.252231] core: cpu_atom PMU driver: PEBS-via-PT
[ 79.252235] ... version: 5
[ 79.252236] ... bit width: 48
[ 79.252237] ... generic registers: 6
[ 79.252237] ... value mask: 0000ffffffffffff
[ 79.252237] ... max period: 00007fffffffffff
[ 79.252238] ... fixed-purpose events: 3
[ 79.252238] ... event mask: 000000070000003f
[ 79.252670] CPU16 is up
[ 79.252682] smpboot: Booting Node 0 Processor 17 APIC 0x4a
[ 79.255669] CPU17 is up
[ 79.255679] smpboot: Booting Node 0 Processor 18 APIC 0x4c
[ 79.258673] CPU18 is up
[ 79.258685] smpboot: Booting Node 0 Processor 19 APIC 0x4e
[ 79.261688] CPU19 is up
[ 79.267182] ACPI: PM: Waking up from system sleep state S3
[ 79.280259] nvme nvme0: 20/0/0 default/read/poll queues
[ 79.281526] nvme nvme1: 20/0/0 default/read/poll queues
[ 79.569437] usb 1-11: reset high-speed USB device number 3 using xhci_hcd
[ 79.580462] ata10: SATA link down (SStatus 0 SControl 300)
[ 79.581160] ata9: SATA link down (SStatus 0 SControl 300)
[ 79.604948] ata6: SATA link down (SStatus 4 SControl 300)
[ 79.605172] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 79.646553] ata5.00: configured for UDMA/100
[ 79.900463] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
[ 79.997841] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[ 79.997871] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 79.997880] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[ 79.997888] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[ 79.998981] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 5
[ 81.096697] OOM killer enabled.
[ 81.096698] Restarting tasks ... done.
[ 81.097300] random: crng reseeded on system resumption
[ 81.100957] PM: suspend exit
[ 81.166992] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 81.277243] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 81.390423] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 84.443459] wlan0: authenticate with 5c:62:8b:44:e7:03
[ 84.446569] wlan0: send auth to 5c:62:8b:44:e7:03 (try 1/3)
[ 84.473910] wlan0: authenticated
[ 84.474137] wlan0: associate with 5c:62:8b:44:e7:03 (try 1/3)
[ 84.476200] wlan0: RX AssocResp from 5c:62:8b:44:e7:03 (capab=0x1011 status=0 aid=19)
[ 84.480809] wlan0: associated
[ 84.535445] wlan0: Limiting TX power to 24 (24 - 0) dBm as advertised by 5c:62:8b:44:e7:03
[ 84.648201] ata7: link is slow to respond, please be patient (ready=0)
[ 84.649209] ata8: link is slow to respond, please be patient (ready=0)
[ 89.328312] ata7: COMRESET failed (errno=-16)
[ 89.329313] ata8: COMRESET failed (errno=-16)
[ 89.899316] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 89.899321] ata7.00: Entering active power mode
[ 90.225843] ata7.00: configured for UDMA/133
[ 92.811319] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 92.811324] ata8.00: Entering active power mode
[ 92.832660] ata8.00: configured for UDMA/133
[ 118.700742] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 118.810699] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 119.025176] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 119.138421] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 119.247161] usb 2-9: current rate 16000 is different from the runtime rate 48000
[ 119.360793] usb 2-9: current rate 16000 is different from the runtime rate 48000
bash-5.2#
When you press ctrl-alt-backspace and your login manager starts a new session a new file /var/log/Xorg.0.log will be started from scratch. However, if you are lucky, you might find some clue why the previous X session crashed from the file /var/log/Xorg.0.log.old.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.