LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-08-2024, 11:35 PM   #1
leigh8904
Member
 
Registered: Nov 2012
Location: Melbourne, Australia
Distribution: Slackware + FreeBSD
Posts: 30

Rep: Reputation: Disabled
5.15.160 kernel causes suspend failure


I just upgraded to 5.15.160 kernel (Slackware64 15.0), along with a bunch of updates from the last month or so.

But now I cannot sleep the system. When I try to sleep (using KDE->Sleep or /bin/loginctl suspend), it goes blank for a while, and then just immediately resumes. When I checked dmesg, I found this:

> Freezing of tasks failed after 20.000 seconds (9 tasks refusing to freeze, wq_busy=0)

The culprit tasks are: lockd (x1), nfsd (x8). Each of these has a message like this:

kernel: task:lockd state:I stack: 0 pid: 1567 ppid: 2 flags:0x00004000
kernel: Call Trace:
kernel: <TASK>
kernel: __schedule+0x2d1/0x1380
kernel: ? kernel_accept+0x8e/0xb0
kernel: ? svc_udp_recvfrom+0x420/0x4a0
kernel: schedule+0x72/0x110
kernel: schedule_timeout+0x11d/0x160
kernel: svc_recv+0x747/0x810
kernel: lockd+0xa9/0x1d0
kernel: ? preempt_count_add+0x70/0xa0
kernel: ? _raw_spin_lock_irqsave+0x19/0x50
kernel: ? set_grace_period+0x90/0x90
kernel: kthread+0x13e/0x170
kernel: ? set_kthread_struct+0x50/0x50
kernel: ret_from_fork+0x1f/0x30
kernel: </TASK>

If I revert to kernel version 5.15.145, sleep / resume all works fine.

Any ideas or suggestions what might be wrong and how to fix it?
 
Old 06-09-2024, 12:22 AM   #2
Nobby6
Member
 
Registered: Jul 2012
Location: Sunshine Coast, Australia
Distribution: Slackware 64
Posts: 241
Blog Entries: 1

Rep: Reputation: 212Reputation: 212Reputation: 212
I just applied last nights kernel update, on 2 machines, my fileserver 32bit installed updates and rebooted fine, the 64bit fileserver has crashed during install.

Installing package kernel-firmware-20240606_90df68d-noarch-1.txz:

PACKAGE DESCRIPTION:
# kernel-firmware (Firmware for the kernel)
#
# These are firmware files for the Linux kernel.
#
# You'll need these to use certain hardware drivers with Linux.
#
# Upstream site:
#
# git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
#


-crashes at this point -
something in repacked 5.15.160-x86-2 is royally screwed...
working sonsole was commanded to reboot 15 minutes ago and is sitting there, looks like a power pull is needed.
 
Old 06-09-2024, 04:19 AM   #3
Petri Kaukasoina
Senior Member
 
Registered: Mar 2007
Posts: 1,960

Rep: Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571
Quote:
Originally Posted by leigh8904 View Post
Any ideas or suggestions what might be wrong and how to fix it?
You could try to find the problem by bisecting between 5.15.145 and 5.15.160. Here are the instructions: https://docs.kernel.org/admin-guide/...roguide-bissbs I have identified a couple of kernel bugs that way, reported them, and got them fixed.

Or, you could try the kernel from -current and use it if it works...
 
Old 06-09-2024, 04:34 AM   #4
Petri Kaukasoina
Senior Member
 
Registered: Mar 2007
Posts: 1,960

Rep: Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571
Quote:
Originally Posted by Nobby6 View Post
I just applied last nights kernel update, on 2 machines, my fileserver 32bit installed updates and rebooted fine, the 64bit fileserver has crashed during install.

Installing package kernel-firmware-20240606_90df68d-noarch-1.txz:

PACKAGE DESCRIPTION:
# kernel-firmware (Firmware for the kernel)
#
# These are firmware files for the Linux kernel.
#
# You'll need these to use certain hardware drivers with Linux.
#
# Upstream site:
#
# git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
#


-crashes at this point -
something in repacked 5.15.160-x86-2 is royally screwed...
working sonsole was commanded to reboot 15 minutes ago and is sitting there, looks like a power pull is needed.
REISUB is cleaner...

So, it crashed already before reboot. If there is a bug somewhere, it's in the previous kernel that your system was running. Which kernel was it? Was it the same 5.15.160 with the -1 version number? Do you have AMD graphics?
 
Old 06-09-2024, 06:38 AM   #5
solarfields
Senior Member
 
Registered: Feb 2006
Location: slackalaxy.com
Distribution: Slackware, CRUX
Posts: 1,457

Rep: Reputation: 1009Reputation: 1009Reputation: 1009Reputation: 1009Reputation: 1009Reputation: 1009Reputation: 1009Reputation: 1009
again this crap?
 
Old 06-09-2024, 07:36 AM   #6
Nobby6
Member
 
Registered: Jul 2012
Location: Sunshine Coast, Australia
Distribution: Slackware 64
Posts: 241
Blog Entries: 1

Rep: Reputation: 212Reputation: 212Reputation: 212
Quote:
Originally Posted by Petri Kaukasoina View Post
REISUB is cleaner...

So, it crashed already before reboot. If there is a bug somewhere, it's in the previous kernel that your system was running. Which kernel was it? Was it the same 5.15.160 with the -1 version number? Do you have AMD graphics?
REISUB = useless

And nope, its Intel, a headless Dell server, that has run without problems, even after the first incarnation of 5.15.160, slackpkg was used to update another package since, I think it was tz package but cant recall to be sure and I don't care enough to go ls -larst'g the package dir, and it was fine, luckily I could revert to previous kernel and with use of rescue usb stick, its all good now, certainly wont be updating any 5.15.160.x kernel again.

That said, this is the first slackware package update thats fouled any of my systems in a couple decades, strange that the 32bit version was all good - but its dell server is much much older (obviously since its 32bit)
 
Old 06-09-2024, 10:41 AM   #7
Petri Kaukasoina
Senior Member
 
Registered: Mar 2007
Posts: 1,960

Rep: Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571
Quote:
Originally Posted by Nobby6 View Post
And nope, its Intel, a headless Dell server, that has run without problems, even after the first incarnation of 5.15.160, slackpkg was used to update another package since, I think it was tz package but cant recall to be sure and I don't care enough to go ls -larst'g the package dir, and it was fine, luckily I could revert to previous kernel and with use of rescue usb stick, its all good now, certainly wont be updating any 5.15.160.x kernel again.
The only difference between the first and the second incarnation of 5.15.160 is a reverted patch on the amdgpu driver. As you don't load the amdgpu.ko module, there is no difference for you. The system crashed while you were installing kernel-firmware, so you hadn't installed the actual kernel packages yet (by alphabetical order). At least you were not running the second incarnation of 5.15.160. Did you revert to kernel 5.15.145?
 
Old 06-09-2024, 11:03 AM   #8
Petri Kaukasoina
Senior Member
 
Registered: Mar 2007
Posts: 1,960

Rep: Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571
Quote:
Originally Posted by Nobby6 View Post
Installing package kernel-firmware-20240606_90df68d-noarch-1.txz:

PACKAGE DESCRIPTION:
# kernel-firmware (Firmware for the kernel)
#
# These are firmware files for the Linux kernel.
#
# You'll need these to use certain hardware drivers with Linux.
#
# Upstream site:
#
# git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
#


-crashes at this point -
Quote:
Originally Posted by Nobby6 View Post
That said, this is the first slackware package update thats fouled any of my systems in a couple decades, strange that the 32bit version was all good
By the way, the kernel-firmware package at which it crashed is exactly the same in all supported Slackware versions, 32/64 bit:
Code:
-rw-r--r-- 4 mirror mirror 333716588 2024-06-08 20:38 slackware-15.0/patches/packages/kernel-firmware-20240606_90df68d-noarch-1.txz
-rw-r--r-- 4 mirror mirror 333716588 2024-06-08 20:38 slackware-current/slackware/a/kernel-firmware-20240606_90df68d-noarch-1.txz
-rw-r--r-- 4 mirror mirror 333716588 2024-06-08 20:38 slackware64-15.0/patches/packages/kernel-firmware-20240606_90df68d-noarch-1.txz
-rw-r--r-- 4 mirror mirror 333716588 2024-06-08 20:38 slackware64-current/slackware64/a/kernel-firmware-20240606_90df68d-noarch-1.txz
(They are hard links to the same inode...)
 
Old 06-10-2024, 01:54 AM   #9
Nobby6
Member
 
Registered: Jul 2012
Location: Sunshine Coast, Australia
Distribution: Slackware 64
Posts: 241
Blog Entries: 1

Rep: Reputation: 212Reputation: 212Reputation: 212
Quote:
Originally Posted by Petri Kaukasoina View Post
The only difference between the first and the second incarnation of 5.15.160 is a reverted patch on the amdgpu driver. As you don't load the amdgpu.ko module, there is no difference for you. The system crashed while you were installing kernel-firmware, so you hadn't installed the actual kernel packages yet (by alphabetical order). At least you were not running the second incarnation of 5.15.160. Did you revert to kernel 5.15.145?
Yes 145, maybe it was bad luck and the first crash of that machine since it was built 5 years ago coincided with a slackpkg update process, I'll maybe try again on the weekend if the forums don't light up, certainly not putting my public facing servers through it though, since 15.1 is probably another 5 years off I might slowly start updating them to current since we are starting to see things unable to build because of those rust loving xxxxxxx's, I swear, rust is a bigger virus then systemd, and I didn't think that was possible
 
Old 06-10-2024, 05:45 AM   #10
bigbadaboum
Member
 
Registered: Apr 2023
Posts: 165

Rep: Reputation: 64
You can send an email to dissatisfaction to the testers.

https://cdn.kernel.org/pub/linux/ker...geLog-5.15.160
Linux 5.15.160

Link: https://lore.kernel.org/r/2024052313...foundation.org
Tested-by: SeongJae Park <sj@kernel.org>
Tested-by: Mark Brown <broonie@kernel.org>
Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
Tested-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
Tested-by: Shuah Khan <skhan@linuxfoundation.org>
Tested-by: Ron Economos <re@w6rz.net>
Tested-by: Kelsey Steele <kelseysteele@linux.microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 
Old 06-10-2024, 12:28 PM   #11
pactel
LQ Newbie
 
Registered: Jun 2024
Posts: 2

Rep: Reputation: 0
I am having the same issue with my install. Slackware 15.0. Been running since released on a clean install. (Not upgraded from 14.x)
I use a custom built kernel config and build/update the kernel regularly. I first noticed a problem with suspend with kernel 5.15.155, sometimes the machine would not resume properly and I was left with a blank screen. I was able to work around this issue by assigning a hotkey to "xrandr - output HDMI-0 -auto", that reset the blanked screen and all was well.

Upon updating to kernel 5.15.160 I had the same issue as the OP. Machine refused to suspend and I get the same errors in syslog.
I had no issue with updating the firmware files, but I run a NVIDIA GPU, so don't think they mattered for this issue.

It is interesting that the issue seems to be on Slackware 15.0 and not noted generally as of yet. Also, a subset of Slackware users who update the kernel and use system suspend.

I downgraded to 5.15.145 and suspend works fine, as the OP noted.
 
Old 06-10-2024, 03:21 PM   #12
leigh8904
Member
 
Registered: Nov 2012
Location: Melbourne, Australia
Distribution: Slackware + FreeBSD
Posts: 30

Original Poster
Rep: Reputation: Disabled
Thanks for the links and comments above. Its been a while since I have compiled kernel, but i guess its like riding a bike. Seemed fairly straight forward, and certainly a lot faster than it used to be on old computer.

Anyway, I confirmed the issue is caused by kernel version 5.15.160; suspend works fine in 5.15.159.

I found out there is a patch impacting nfsd https://lore.kernel.org/all/20240523...oundation.org/, it could be the culprit.
 
2 members found this post helpful.
Old 06-10-2024, 04:44 PM   #13
414N
Member
 
Registered: Sep 2011
Location: Italy
Distribution: Slackware
Posts: 648

Rep: Reputation: 189Reputation: 189
hang on resume from suspend 2 disk (hibernation)

I had issues too after upgrading to the first and then the second "incarnation" of the 5.15.160 kernel update on Slackware64 15.0.

The suspend to disk stopped working when resuming the system: I could see the desktop or the terminal from which I started the hibernation, but the screen was completely frozen and the system unresponsive. The keyboard (a Corsair K55) did not light up even after some time, and I could only physically reset the machine.

The system sports an AMD RX590 GPU so I thought that the second kernel 5.15.160 package would fix the issue, but it persisted.

Thinking that the issue stemmed from the graphics driver, I did try to add some "well-known" kernel options at boot (pcie_aspm=off, amdgpu.runpm=0) to no avail.

After downgrading the kernel packages using the cumulative patch server and removing any extra kernel boot argument I found that the issue was no more.

PS: I kept the updated kernel-firmware package with no issues.

Last edited by 414N; Yesterday at 03:27 AM. Reason: fix bbcode
 
Old 06-10-2024, 08:37 PM   #14
Nobby6
Member
 
Registered: Jul 2012
Location: Sunshine Coast, Australia
Distribution: Slackware 64
Posts: 241
Blog Entries: 1

Rep: Reputation: 212Reputation: 212Reputation: 212
Quote:
Originally Posted by bigbadaboum View Post
You can send an email to dissatisfaction to the testers.

https://cdn.kernel.org/pub/linux/ker...geLog-5.15.160
Linux 5.15.160

Link: https://lore.kernel.org/r/2024052313...foundation.org
Tested-by: SeongJae Park <sj@kernel.org>
Tested-by: Mark Brown <broonie@kernel.org>
Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
Tested-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
Tested-by: Shuah Khan <skhan@linuxfoundation.org>
Tested-by: Ron Economos <re@w6rz.net>
Tested-by: Kelsey Steele <kelseysteele@linux.microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
I have GKH's personal Email, known him 20 years, I was thinking of letting him know what
I think of it if it fails again
 
Old Yesterday, 12:16 AM   #15
Petri Kaukasoina
Senior Member
 
Registered: Mar 2007
Posts: 1,960

Rep: Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571
Quote:
Originally Posted by leigh8904 View Post
I found out there is a patch impacting nfsd https://lore.kernel.org/all/20240523...oundation.org/, it could be the culprit.
Yes, it's reported here: https://lore.kernel.org/all/8ddb4da3...1b@nvidia.com/

Last edited by Petri Kaukasoina; Yesterday at 01:15 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] 5.15.160 kernel breaks amdgpu driver fsLeg Slackware 4 06-09-2024 03:05 AM
[SOLVED] Failure after failure after failure.....etc 69Rixter Linux - Laptop and Netbook 5 04-14-2015 09:58 AM
how to configure sound in GNU/debian sarge kernel 2.6 for toshiba satellite m30x-160 manda-chuva Linux - Laptop and Netbook 1 04-13-2005 08:47 PM
Can you find the error ? (160 lines) math-cases etc Dimitris Programming 5 09-02-2003 04:42 PM
RH 7.0 Adding Promise ATA 100 Card and 160 gig drive lsgko Linux - Newbie 1 08-05-2003 04:33 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:26 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration