cross-posted from: https://lemmy.world/post/1313651
Every time I plug in my Quadcast S USB mic into my Arch Linux box, I can’t properly go into deep sleep. Unplugging it before attempting to sleep makes it work again, but its annoying to have to do that every time. How do I debug this and where do I even submit a bug report for this?
Here’s the relevant journalctl:
Jul 10 11:59:39 systemd[1]: Starting System Suspend... Jul 10 11:59:39 systemd-sleep[70254]: Entering sleep state 'suspend'... Jul 10 11:59:39 kernel: PM: suspend entry (deep) Jul 10 11:59:39 kernel: Filesystems sync: 0.066 seconds Jul 10 11:59:42 kernel: Freezing user space processes Jul 10 11:59:42 kernel: Freezing user space processes completed (elapsed 0.001 seconds) Jul 10 11:59:42 kernel: OOM killer disabled. Jul 10 11:59:42 kernel: Freezing remaining freezable tasks Jul 10 11:59:42 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) Jul 10 11:59:42 kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jul 10 11:59:42 kernel: serial 00:04: disabled Jul 10 11:59:42 kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 10 11:59:42 kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache Jul 10 11:59:42 kernel: sd 5:0:0:0: [sdc] Synchronizing SCSI cache Jul 10 11:59:42 kernel: sd 1:0:0:0: [sda] Stopping disk Jul 10 11:59:42 kernel: sd 2:0:0:0: [sdb] Stopping disk Jul 10 11:59:42 kernel: sd 5:0:0:0: [sdc] Stopping disk Jul 10 11:59:42 kernel: ACPI: PM: Preparing to enter system sleep state S3 Jul 10 11:59:42 kernel: ACPI: PM: Saving platform NVS memory Jul 10 11:59:42 kernel: Disabling non-boot CPUs ... Jul 10 11:59:42 kernel: Wakeup pending. Abort CPU freeze Jul 10 11:59:42 kernel: Non-boot CPUs are not disabled Jul 10 11:59:42 kernel: ACPI: PM: Waking up from system sleep state S3 Jul 10 11:59:42 kernel: sd 5:0:0:0: [sdc] Starting disk Jul 10 11:59:42 kernel: sd 2:0:0:0: [sdb] Starting disk Jul 10 11:59:42 kernel: sd 1:0:0:0: [sda] Starting disk Jul 10 11:59:42 kernel: serial 00:04: activated
Thanks in advance!
You must log in or # to comment.