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

2020-12-09 Thread Matthijs
...and my (probably) final report to this mailing list: The most recent crashes/hangs I experienced have no relation to Debian release or Linux kernel, but most likely a hardware issue. I initially experienced a crash similar to what the original report in this bug-thread showed. Suspecting

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

2020-11-11 Thread Matthijs
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

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

2020-11-03 Thread tobias
i upgraded myself today to 4.19.0-12 (or 4.19.152-1 according to upstream version numbers) no issue yet. this blog contains some interesting info: http://blog.pi3.com.pl/?p=720 both CVE's mentioned are fixed now in debian https://security-tracker.debian.org/tracker/CVE-2020-25220

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

2020-10-21 Thread debian-968335
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

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

2020-10-18 Thread Mark Wahl
Hi, just wanted to report that after using kernel 4.19.0-11-amd64 my system is stable again (uptime now more than 1 week) and the message is no more seen in the logs. So problem is solved at least on my system. Bye,wahlm

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

2020-10-01 Thread Matthijs van Aalten
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

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

2020-09-20 Thread Mark Wahl
Hello, my gigabyte brix system (Celeron J3160) worked rock solid 24/7 up to now (stretch install, upgrade to buster) as a small server with zabbix/mariadb, some kvm virtual machines and docker containers. Mass storage is at 2 usb3 2T disks. After updating the kernel to  4.19.0-10-amd64 (Debian

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

2020-08-13 Thread tobias
Hello, wanted to add that the issue gets triggered when running the following script: #!/bin/sh if [ -x /usr/bin/certbot ]; then certbot -q--authenticator standalone \ --installer none renew \ --pre-hook "service apache2 stop" \ --post-hook

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

2020-08-13 Thread tobias
Package: src:linux Version: 4.19.132-1 Severity: critical -- Package-specific info: ** Version: Linux version 4.19.0-10-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.132-1 (2020-07-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-amd64