Your message dated Sat, 15 May 2021 06:10:54 -0700 (PDT)
with message-id <609fc85e.1c69fb81.92e10.6...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #864312,
regarding BUG: soft lockup - CPU#0 stuck for 22s!
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 ow...@bugs.debian.org
immediately.)


-- 
864312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.16.0-4-amd64
Version: 3.16.43-2

Hi!

After upgrade kernel to 3.16.43-2 version I have faced with strange bug that 
never seen before in Debian. My server became unresponsive after couple hours 
after boot. Couple times I saw error «BUG: soft lockup - CPU#0 stuck for 22s!» 
that I see on the console. Server became to normal work only when I unplug 
power cord from the server and plug it back after 10-20 seconds. This bug 
appears randomly and not depend from software that I’m using or from additional 
hardware that I connecting to the server (for example, I have installed GPU and 
bug still present).

Also I have tested two kernels from back ports. They are listed below:

Package: linux-image-4.9.0-0.bpo.2-amd64
Version: 4.9.18-1~bpo8+1

Package: linux-image-4.9.0-0.bpo.3-amd64
Version: 4.9.25-1~bpo8+1

On those two kernels bug reproducing well on my peace of hardware.

After a month of suffering I was forced to roll back to stable kernel version 
that works well without any issues:

Package: linux-image-3.16.0-4-amd64
Version: 3.16.39-1+deb8u2

I’m using Hewlett Packard ProLiant MicroServer G7 N40L.

If you will have additional questions or need more information please let me 
know.

Please, advice.

Thanks, Serhiy

--- 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 via email to