On Mon, 15 May 2023 18:30:31, David wrote:
On Mon, 2023-05-15 at 11:17 +0300, Anssi Saari wrote:
Christian Gelinek <cgeli...@radlogic.com.au> writes:
> Is anyone else seeing a similar problem? What can I do to avoid
> this?
> Do we need anything else to narrow it down further?
Only time I've seen a soft lockup was from a bad CPU. There were a
bunch
of them and eventually the computer hung. Going back to the slow
plodding Celeron fixed all issues. Except CPU performance of course.
It's happened to me a couple of times, but only since I switched from
stable to testing, over the last month.
As I don't think everybody is running a Dell 980 desktop, or the same
desktop environment, it's probably not a hardware/software mismatch.
We'd be looking at strictly software, I suspect.
I have the same hunch. I got that PC new on Feb 20th, so I hope it's not
the CPU. It also happened just twice since then, even though I keep it
running pretty much 24/7. Not doing very much when I'm not there, which
was the case both times.
And for both times, the journalctl log looks suspiciously similar,
starting with the snd_hda_intel entry.
First time:
Apr 10 07:36:07 gar systemd[1]: anacron.service: Deactivated successfully.
Apr 10 07:50:01 gar kernel: snd_hda_intel 0000:04:00.0: Unable to change
power state from D3hot to D0, device inaccessible
Apr 10 07:50:03 gar kernel: [drm:fw_domains_get_with_fallback [i915]]
*ERROR* render: timed out waiting for forcewake ack to clear.
Apr 10 07:50:03 gar kernel: i915 0000:03:00.0: [drm:add_taint_for_CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
...
Second time:
May 14 00:17:01 gar CRON[2929]: pam_unix(cron:session): session closed
for user root
May 14 00:54:00 gar kernel: snd_hda_intel 0000:04:00.0: Unable to change
power state from D3hot to D0, device inaccessible
May 14 00:54:03 gar kernel: [drm:fw_domains_get_with_fallback [i915]]
*ERROR* render: timed out waiting for forcewake ack to clear.
May 14 00:54:03 gar kernel: i915 0000:03:00.0: [drm:add_taint_for_CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
...
To reproduce it, I'd probably have to somehow trigger the condition
manually, any ideas?
Thanks for your time!
