Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Unfortunately, I seem to be suffering from the same issue.
Initially I thought it was a hardware issue (system was ~10 years old), so I replaced the Intel DH67CF with core2duo processor by an Asrock H470M-ITX and Intel i5-10400 processor (and new case, new power supply; only SSD is re-used).
A screenshot I made of a kernel crash ~3 weeks ago showed the same message as in the original bug report. With the new hardware, I suffered from a crash this weekend (still the 4.19.0-10-amd64 kernel).
I wasn't able to reproduce the issue at will - it just happened randomly, it seems. But I did have the impression that, at least on three times, it happened when another Debian box was booted and made an NFS connection to the problematic machine. So could be ethernet related.
And to agree with Mike above: indeed, I have a docker container operational.
So far with the new kernel, no crash yet - but I did get this kernel call trace:
Sep 30 08:24:30 vanaalten kernel: [159962.295249] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.19.0-11-amd64 #1 Debian 4.19.146-1
Sep 30 08:24:30 vanaalten kernel: [159962.295338] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H470M-ITX/ac, BIOS P1.20 05/18/2020
Sep 30 08:24:30 vanaalten kernel: [159962.295348] RIP: 0010:cpuidle_enter_state+0xb9/0x320
Sep 30 08:24:30 vanaalten kernel: [159962.295352] Code: e8 9c b5 b0 ff 80 7c 24 0b 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3b 02 00 00 31 ff e8 ce a7 b6 ff fb 66 0f 1f 44 00 00 <48> b8 ff ff ff ff f3 01 00 00 48 2b 1c 24 ba ff ff ff 7f 48 39 c3
Sep 30 08:24:30 vanaalten kernel: [159962.295354] RSP: 0018:ffffbe03019a3e90 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffde
Sep 30 08:24:30 vanaalten kernel: [159962.295358] RAX: ffff9c1bcf5620c0 RBX: 0000917c1fc829ea RCX: 000000000000001f
Sep 30 08:24:30 vanaalten kernel: [159962.295360] RDX: 0000917c1fc829ea RSI: 000000002c13c01d RDI: 0000000000000000
Sep 30 08:24:30 vanaalten kernel: [159962.295362] RBP: ffff9c1bc4d13000 R08: 0000000000000002 R09: 0000000000021980
Sep 30 08:24:30 vanaalten kernel: [159962.295363] R10: 0001a685134b4b1d R11: ffff9c1bcf5610a8 R12: 0000000000000003
Sep 30 08:24:30 vanaalten kernel: [159962.295365] R13: ffffffff94aba518 R14: 0000000000000003 R15: 0000000000000000
Sep 30 08:24:30 vanaalten kernel: [159962.295368] FS: 0000000000000000(0000) GS:ffff9c1bcf540000(0000) knlGS:0000000000000000
Sep 30 08:24:30 vanaalten kernel: [159962.295370] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 30 08:24:30 vanaalten kernel: [159962.295372] CR2: 0000561438923229 CR3: 00000001ef40a006 CR4: 00000000003606e0
Sep 30 08:24:30 vanaalten kernel: [159962.295374] Call Trace:
Sep 30 08:24:30 vanaalten kernel: [159962.295386] do_idle+0x228/0x270
Sep 30 08:24:30 vanaalten kernel: [159962.296362] cpu_startup_entry+0x6f/0x80
Sep 30 08:24:30 vanaalten kernel: [159962.296367] start_secondary+0x1a4/0x200
Sep 30 08:24:30 vanaalten kernel: [159962.296373] secondary_startup_64+0xa4/0xb0
...but the system is still fully operational.
No idea how serious above call trace is. Hopefully no further crashes.
--
Matthijs
Reply to: