Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #68413 > unrolled thread
| Started by | debian-968335@vanaalten.net |
|---|---|
| First post | 2020-10-21 15:10 +0200 |
| Last post | 2020-10-21 15:10 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
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
| From | debian-968335@vanaalten.net |
|---|---|
| Date | 2020-10-21 15:10 +0200 |
| Subject | Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120 |
| Message-ID | <B2m2l-6hN-5@gated-at.bofh.it> |
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 top | Article view | linux.debian.kernel
csiph-web