Bug#859856: marked as done (4.9.13-1~bpo8+1 and SuperMicro X10DRT-PT kernel trace)

["Debian Bug Tracking System" <owner@bugs.debian.org>]

Your message dated Sun, 23 May 2021 20:56:43 +0200
with message-id <E1lktHA-0006NP-EB@hullmann.westfalen.local>
and subject line Closing this bug
has caused the Debian Bug report #859856,
regarding 4.9.13-1~bpo8+1 and SuperMicro X10DRT-PT kernel trace
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.)


-- 
859856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859856
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- Begin Message ---

• To: submit@bugs.debian.org
• Subject: 4.9.13-1~bpo8+1 and SuperMicro X10DRT-PT kernel trace
• From: Rumen Telbizov <telbizov@gmail.com>
• Date: Fri, 7 Apr 2017 13:26:53 -0700
• Message-id: <CAENR+_VYkWTsDZhMUPAbGegy1=He8LVATbiToZC23+aJV+sFhQ@mail.gmail.com>

Package: linux-image-4.9.0-0.bpo.2-amd64

Version: 4.9.13-1~bpo8+1

Severity: important

Dear Debian maintainers,

I would like to report a reproducible kernel stack trace that we started to experience after we upgraded the kernel on some of our hosts running a specific motherboard/CPU model.

OS: Debian 8.7 Jessie (up-to-date)

Offending kernel: 4.9.13-1~bpo8+1 (from jessie-backports)

Motherboard: X10DRT-PT (SuperMicro)

CPU: 2 x E5-2620 v4 @ 2.10GHz

RAM: 128GB

The stack trace is:

[  245.006408] INFO: task systemd-udevd:552 blocked for more than 120 seconds.

[  245.006467]       Not tainted 4.9.0-0.bpo.2-amd64 #1

[  245.006501] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[  245.006552] systemd-udevd   D    0   552    547 0x00000004

[  245.006557]  ffff95a5744f7800 0000000000000000 ffff95b578530100 ffff95a577ade100

[  245.006561]  ffff95b57f458700 ffffb8bc0d7a3b50 ffffffffaa1f668d 0000000000001257

[  245.006565]  ffff95a577ade100 00000000a9c2476b ffff95a500000001 ffff95a577ade100

[  245.006569] Call Trace:

[  245.006579]  [<ffffffffaa1f668d>] ? __schedule+0x23d/0x6d0

[  245.006594]  [<ffffffffc096de30>] ? uncore_pci_remove+0x160/0x160 [intel_uncore]

[  245.006597]  [<ffffffffaa1f6b52>] ? schedule+0x32/0x80

[  245.006599]  [<ffffffffaa1fa089>] ? schedule_timeout+0x249/0x300

[  245.006602]  [<ffffffffaa1f6695>] ? __schedule+0x245/0x6d0

[  245.006609]  [<ffffffffc096d554>] ? uncore_alloc_box+0x74/0xd0 [intel_uncore]

[  245.006615]  [<ffffffffa9c2ed05>] ? sched_clock+0x5/0x10

[  245.006622]  [<ffffffffc096de30>] ? uncore_pci_remove+0x160/0x160 [intel_uncore]

[  245.006633]  [<ffffffffaa1f756a>] ? wait_for_completion+0xfa/0x130

[  245.006640]  [<ffffffffa9ca2b30>] ? wake_up_q+0x60/0x60

[  245.006644]  [<ffffffffa9c791d6>] ? cpuhp_issue_call+0x96/0xc0

[  245.006646]  [<ffffffffa9c7948a>] ? __cpuhp_setup_state+0xca/0x200

[  245.006656]  [<ffffffffc098c317>] ? intel_uncore_init+0x1c1/0xeaa [intel_uncore]

[  245.006665]  [<ffffffffc098c156>] ? uncore_type_init+0x156/0x156 [intel_uncore]

[  245.006670]  [<ffffffffa9c0218c>] ? do_one_initcall+0x4c/0x180

[  245.006676]  [<ffffffffa9d7c3af>] ? do_init_module+0x5a/0x1f1

[  245.006679]  [<ffffffffa9d01de9>] ? load_module+0x23c9/0x28f0

[  245.006682]  [<ffffffffa9cfe650>] ? __symbol_put+0x60/0x60

[  245.006687]  [<ffffffffa9e033a4>] ? vfs_read+0x114/0x130

[  245.006693]  [<ffffffffa9ea3e01>] ? security_capable+0x41/0x60

[  245.006696]  [<ffffffffa9d024fe>] ? SYSC_finit_module+0x8e/0xe0

[  245.006700]  [<ffffffffaa1fb3fb>] ? system_call_fast_compare_end+0xc/0x9b

The above occurs briefly after boot and leaves systemd-udevd stuck in 'D' state. It is worth mentioning that we tried running the above kernel on a bunch of different SuperMicro motherboards (X8/X9 generation) without any problems.

Let me know if I can provide additional information.

Thank you,

--

Rumen Telbizov

Unix Systems Administrator

--- End Message ---

--- Begin Message ---

• To: 859856-done@bugs.debian.org
• Subject: Closing this bug
• From: jmm@debian.org
• Date: Sun, 23 May 2021 20:56:43 +0200
• Message-id: <E1lktHA-0006NP-EB@hullmann.westfalen.local>

This bug was filed for a very old kernel. If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from buster.backports
please reopen the bug, see https://www.debian.org/Bugs/server-control

--- End Message ---