Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120

To: 968335@bugs.debian.org
Subject: Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
From: Matthijs <debian-968335@vanaalten.net>
Date: Thu, 12 Nov 2020 08:11:16 +0100
Message-id: <[🔎] 20201112071116.GA12594@vanaalten.net>
Reply-to: Matthijs <debian-968335@vanaalten.net>, 968335@bugs.debian.org
In-reply-to: <[🔎] em7b73a980-d742-492f-90a5-bce68605fbbd@desktop-qjhjrs6>
References: <563b2f72-89a5-f5a4-ed81-ff59e4eb5b92@vanaalten.net> <159730646912.12125.6713504224016349614.reportbug@serafijn.appelo.org> <[🔎] em7b73a980-d742-492f-90a5-bce68605fbbd@desktop-qjhjrs6> <159730646912.12125.6713504224016349614.reportbug@serafijn.appelo.org>

Unfortunately, my machine crashed again last night. No special activity, no stressing things going on - just full 100% standstill.

Nothing visible in either syslog or kern.log. On screen just the regular login prompt (no GUI, just terminal login) but the cursor was absent and the system didn't react to keyboard.

So, also unfortunately, no error log or crash information at all. So don't know if the crashes I experience are in any way related to this kernel bug #968335

Any suggestions how I can get any further information out of this system in future crashes?

Kind regards,
Matthijs

Reply to:

References:
- Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
  - From: tobias <tobias@appelo.org>

Prev by Date: Bug#974528: Regression: built-in ethernet on PINE A64+ stopped working (dwmac-sun8i)
Next by Date: Processed: tagging 868771
Previous by thread: Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Next by thread: Bug#973733: RTW88_8821ce module fails to find firmware during install and must be reloaded
Index(es):
- Date
- Thread