On Wed, 17 May 2023 02:12:32 +0100, Philip Wyett wrote:
A little research shows that this is not that uncommon. A suggested
workaround is to disable the
power management for the device as follows.
Create a file (such as):
/etc/modprobe.d/snd-intel-disable-power-management.conf
Add the following line: options snd_hda_intel power_save=0
Reboot.
Hopefully this may assist.
I tried:
$ ls -l /etc/modprobe.d/snd-intel-disable-power-management.conf
-rw-r----- 1 root root 36 May 23 10:01
/etc/modprobe.d/snd-intel-disable-power-management.conf
$ sudo cat /etc/modprobe.d/snd-intel-disable-power-management.conf
options snd_hda_intel power_save=0
Nevertheless, this morning I arrived to the locked-up state. Journalctl
output:
May 31 04:17:01 gar CRON[2175]: (root) CMD (cd / && run-parts --report
/etc/cron.hourly)
May 31 04:17:01 gar CRON[2174]: pam_unix(cron:session): session closed
for user root
May 31 05:12:00 gar kernel: snd_hda_intel 0000:04:00.0: Unable to change
power state from D3hot to D0, device inaccessible
May 31 05:12:03 gar kernel: [drm:fw_domains_get_with_fallback [i915]]
*ERROR* render: timed out waiting for forcewake ack to clear.
May 31 05:12:03 gar kernel: i915 0000:03:00.0: [drm:add_taint_for_CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x>
May 31 05:12:07 gar kernel: INFO: NMI handler (perf_event_nmi_handler)
took too long to run: 84.155 msecs
May 31 05:12:07 gar kernel: perf: interrupt took too long (657458 >
2500), lowering kernel.perf_event_max_sample_rate to 250
May 31 05:12:07 gar kernel: [drm:fw_domains_get_with_fallback [i915]]
*ERROR* render: timed out waiting for forcewake ack to clear.
May 31 05:12:07 gar kernel: i915 0000:03:00.0: [drm:add_taint_for_CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x>
May 31 05:12:11 gar kernel: [drm:fw_domains_get_with_fallback [i915]]
*ERROR* render: timed out waiting for forcewake ack to clear.
May 31 05:12:11 gar kernel: i915 0000:03:00.0: [drm:add_taint_for_CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x>
May 31 05:12:15 gar kernel: [drm:fw_domains_get_with_fallback [i915]]
*ERROR* gt: timed out waiting for forcewake ack to clear.
May 31 05:12:15 gar kernel: i915 0000:03:00.0: [drm:add_taint_for_CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x>
May 31 05:12:16 gar kernel: i915 0000:03:00.0: [drm] *ERROR* CT:
Corrupted descriptor head=4294967295 tail=4294967295 status=0xfffff>
May 31 05:12:27 gar kernel: [drm:fw_domains_get_with_fallback [i915]]
*ERROR* render: timed out waiting for forcewake ack to clear.
May 31 05:12:27 gar kernel: i915 0000:03:00.0: [drm:add_taint_for_CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x>
May 31 05:12:27 gar kernel: [drm:fw_domains_get_with_fallback [i915]]
*ERROR* gt: timed out waiting for forcewake ack to clear.
May 31 05:12:27 gar kernel: i915 0000:03:00.0: [drm:add_taint_for_CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x>
May 31 05:12:27 gar kernel: watchdog: BUG: soft lockup - CPU#14 stuck
for 26s! [kworker/14:2:2123]
May 31 05:12:27 gar kernel: Modules linked in: snd_seq_dummy snd_hrtimer
snd_seq snd_seq_device nfsv3 nfs_acl rpcsec_gss_krb5 auth_r>
May 31 05:12:27 gar kernel: intel_uncore wmi_bmof ee1004 pcspkr
watchdog soundcore intel_vsec serial_multi_instantiate intel_pmc_co>
May 31 05:12:27 gar kernel: CPU: 14 PID: 2123 Comm: kworker/14:2
Tainted: G U W 6.1.0-9-amd64 #1 Debian 6.1.27-1
May 31 05:12:27 gar kernel: Hardware name: Micro-Star International Co.,
Ltd. MS-7E02/PRO B760M-P DDR4 (MS-7E02), BIOS 1.00 10/21/20>
May 31 05:12:27 gar kernel: Workqueue: pm pm_runtime_work
May 31 05:12:27 gar kernel: RIP: 0010:pci_mmcfg_read+0xb0/0xe0
May 31 05:12:27 gar kernel: Code: 5d 41 5e 41 5f c3 cc cc cc cc 4c 01 e0
66 8b 00 0f b7 c0 89 45 00 eb dc 4c 01 e0 8a 00 0f b6 c0 89>
May 31 05:12:27 gar kernel: RSP: 0018:ffffb5ce87b9bcc0 EFLAGS: 00000286
May 31 05:12:27 gar kernel: RAX: 00000000ffffffff RBX: 0000000000400000
RCX: 0000000000000ffc
May 31 05:12:27 gar kernel: RDX: 00000000000000ff RSI: 0000000000000004
RDI: 0000000000000000
May 31 05:12:27 gar kernel: RBP: ffffb5ce87b9bcfc R08: 0000000000000004
R09: ffffb5ce87b9bcfc
May 31 05:12:27 gar kernel: R10: 0000000000000004 R11: ffffffffb19a70a0
R12: 0000000000000ffc
May 31 05:12:27 gar kernel: R13: 0000000000000000 R14: 0000000000000004
R15: 0000000000000000
May 31 05:12:27 gar kernel: FS: 0000000000000000(0000)
GS:ffff9c641fb80000(0000) knlGS:0000000000000000
May 31 05:12:27 gar kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
May 31 05:12:27 gar kernel: CR2: 00007f78df2005c9 CR3: 000000010571e005
CR4: 0000000000770ee0
May 31 05:12:27 gar kernel: PKRU: 55555554
May 31 05:12:27 gar kernel: Call Trace:
May 31 05:12:27 gar kernel: <TASK>
May 31 05:12:27 gar kernel: pci_bus_read_config_dword+0x46/0x80
May 31 05:12:27 gar kernel: pci_find_next_ext_capability+0x82/0xe0
May 31 05:12:27 gar kernel: ? pci_conf1_read+0x9b/0xf0
May 31 05:12:27 gar kernel: pci_restore_state.part.0+0x5d/0x3a0
May 31 05:12:27 gar kernel: pci_pm_runtime_resume+0x41/0xe0
May 31 05:12:27 gar kernel: ? pci_pm_restore_noirq+0xc0/0xc0
May 31 05:12:27 gar kernel: __rpm_callback+0x41/0x170
May 31 05:12:27 gar kernel: ? pci_pm_restore_noirq+0xc0/0xc0
May 31 05:12:27 gar kernel: rpm_callback+0x5d/0x70
May 31 05:12:27 gar kernel: ? pci_pm_restore_noirq+0xc0/0xc0
May 31 05:12:27 gar kernel: rpm_resume+0x5df/0x820
May 31 05:12:27 gar kernel: pm_runtime_work+0x6c/0xa0
May 31 05:12:27 gar kernel: process_one_work+0x1c4/0x380
May 31 05:12:27 gar kernel: worker_thread+0x4d/0x380
May 31 05:12:27 gar kernel: ? _raw_spin_lock_irqsave+0x23/0x50
May 31 05:12:27 gar kernel: ? rescuer_thread+0x3a0/0x3a0
May 31 05:12:27 gar kernel: kthread+0xe6/0x110
May 31 05:12:27 gar kernel: ? kthread_complete_and_exit+0x20/0x20
May 31 05:12:27 gar kernel: ret_from_fork+0x1f/0x30
May 31 05:12:27 gar kernel: </TASK>
-- Boot 8206a74ca5a54b4c98a1ee6b0586771c --
Maybe I should try to upgrade the BIOS, as suggested by Xiyue Deng [0]
when I get a chance.
Thanks for your time!
[0]: https://lists.debian.org/debian-user/2023/05/msg00749.html
