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

Bug#851119: marked as done (4.8.11 bpo8: "list_del corruption" and "CPU#x got stuck for 22s")

Your message dated Sat, 15 May 2021 04:51:06 -0700 (PDT)
with message-id <609fb5aa.1c69fb81.9fb82.685c@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #851119,
regarding 4.8.11 bpo8: "list_del corruption" and "CPU#x got 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 owner@bugs.debian.org
immediately.)


-- 
851119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851119
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-4.8.0-0.bpo.2-amd64-unsigned
Version: 4.8.11-1~bpo8+1
Hi folks,

I have the impression that there is an increased probability
for linux-image-4.8.0-0.bpo.2-amd64-unsigned (4.8.11-1~bpo8+1)
to run into "CPU#x got stuck for 22s" messages.

The hosts with 4.7 (4.7.8-1~bpo8+1) don't show this.

logfile is attached. I know that a bpo kernel is not the highest
priority right now, but maybe somebody could take a look?


Thanx in advance
Harri

Attachment: kern.log.gz
Description: application/gzip


--- 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: