linuxmint / linuxmint/mintupdate
Kernel upgrade to 7.0.0.28 kills proper shutdown
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 425
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
After upgrading to kernel 7.0.0.28 I observe the shutdown process does not complete anymore and the light indicating the PC is working stays on.
To Reproduce
Steps to reproduce the behavior:
- Upgrade Kernel 7.0.0.28 (assumption)
- Boot into Linux mint
- Any type of shutdown- via console or any GUI
- Error: Shutdown "nearly" completes, screen blank- but the power led indicator -and sometimes the ventilator- stays on. Need to hard-/longpress the on/on button to achieve a proper power off status.
Distribution:
- [ X] Linux Mint 22.3
Software version:
Kernel 7.0.0.28
Logs:
I don't know how to get journalctl to show the last boot logs.. (?) it only shows me from the actual session.
Device (if relevant)
Lenovo Ideapad Slim 3 15AHP10 (AMD Ryzen 7)
Side notes
-I had also hibernation issues and extended my swap partition to 16GB, but that didn't resolve it.
-Seems to be an issue of the kernel version, not from ubuntu or mint or mintupdate- please reassign as it fits.
I go back to 6.17 kernel
https://www.reddit.com/r/linuxmint/comments/1v45pji/confirmed_regression_shutdown_hangs_fails_to/
(If I should log this in another section of the linuxmint github, pls let me know for next time, not familiar with the structure of this github)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No project files or tests are named; begin by reproducing shutdown behavior on Linux Mint 22.3 with kernel 7.0.0.28 and comparing it with 6.17. Learn how to capture the final boot's journal logs with journalctl, and consider the report complete when the regression is reproducible and its responsible component is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100