[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#946195: marked as done (Kernel 4.19 bug soft lookup CPU stuck)

Your message dated Thu, 20 Feb 2025 12:38:18 +0100 (CET)
with message-id <20250220113818.3BDDABE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #946195,
regarding Kernel 4.19 bug soft lookup CPU stuck
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
946195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946195
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- Package: linux-image-4.19.0-6-amd64

Version: 4.19.67-2+deb10u2


After i've upgraded some computers from stretch to buster i got strange CPU error when i switch on or off the machine.

This is the error i got:

systemd-journald[287]: Failed to send WATCHDOG=1 notification message: Connection refused.
rcu: INFO: rcu_sched self-detected stall on CPU
rcu: 1-....: (5249 ticks this GP) idle=bce/1/0x40000000000000002 softirq=103055/103055 fqs=2374
rcu: (t=5250 jiffies g=179473 q=1)
watchdog: BUG: soft lookup - CPU#1 stuck for 22s! [systemd-shutdown:1]

If this issue show up when i turn on the computer, i have to force the shutdown and turn on again (hoping it wouldn't show up again).

If this issue show up when i turn off the machine, instead, it simply remains stucked until someone don't force the shut down.

I tried to change kernel to buster-backports linux-image-5.2.0-0.bpo.3-rt-amd64, this error disappeared but i got some issues with third party java's application.
So i tried to modify some kernel params:

sysctl -w kernel.watchdog_thresh=20
sysctl -w kernel.nmi_watchdog=0

and

echo blacklist sp5100_tco > /etc/modprobe.d/nmi-blacklist.conf

in /etc/default/grub i changed

GRUB_CMDLINE_LINUX_DEFAULT="nmi_watchdog=0 memory_corruption_check=0 quiet"

but nothing happened.

In the end, i was forced to install kernel 4.9 from stretch (4.9.0-11-amd64) and this error disappeared.

There is something i can try to fix this?

Thank you,

Lori
AVVISO: Questo messaggio e' inviato da Banca Sammarinese di Investimento S.p.A. e puo' contenere informazioni di carattere estremamente riservato e confidenziale. Qualsivoglia utilizzo non autorizzato del contenuto di questo messaggio costituisce violazione dell'obbligo di non prendere cognizione della corrispondenza tra altri soggetti, salvo piu' grave illecito ed espone il responsabile alle relative conseguenze. Qualora non foste i destinatari, vogliate immediatamente informarci con lo stesso mezzo ed eliminare il messaggio, con gli eventuali allegati, senza trattenerne copia. Grazie per la collaborazione. DISCLAIMER: This e-mail contains confidential information, which is intended only for the use of the recipient(s) named above. If you have received this communication in error, please notify the sender immediately via e-mail and return the entire message. Thank you for your assistance.

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: