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

From	debian-968335@vanaalten.net
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Date	2020-10-21 15:10 +0200
Message-ID	<B2m2l-6hN-5@gated-at.bofh.it> (permalink)
References	<B1i0N-8g6-11@gated-at.bofh.it> <ADgCR-2LM-1@gated-at.bofh.it> <B1i0N-8g6-9@gated-at.bofh.it> <ADgCR-2LM-1@gated-at.bofh.it> <B1i0N-8g6-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

Unfortunately I'm not 100% convinced yet.

I suffered from hangs with the 4.19.0-10 kernel; on 4.19.0-11 I got at 
least a similar warning message on screen (see 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968335#27), and last 
saturday I also got a completely hanging system - without any feedback 
in either kern.log, syslog or even on screen. Not responding to 
keyboard. Only similarity I see is that syslog contains a bunch of 
0-bytes at the time of the incident.

While I didn't get anything indicating that this is the same issue as 
before, I'm not convinced that the issue is resolved.

But, I also got a new kernel version (4.19.0-12) today - let's see if 
this one is more stable.

Regards,
Matthijs

Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread

Thread

Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120 debian-968335@vanaalten.net - 2020-10-21 15:10 +0200

csiph-web