Hello,This could be due to a new bug introduced into the kernel, in which case you should file a bug on the kernel. The other issue it could be, is that the package maintainer which built the latest version of the kernel has changed the configuration for the kernel thus not compiling in the features you need for the suspending to work.
Jan Alexander Steffens was the last packager for the kernel, if any of the Linux package maintainers are subscribed to this mailing list, your support would be useful to figure out if it is a kernel configuration issue, or an issue with the kernel codebase.
Looking at the commit (on github) which updated the kernel: https://github.com/archlinux/svntogit-packages/commit/fdde8b0bbded69507f5e76e47978e4c38e92c327The only thing which was changed is the package version, thus the configuration was not changed.
Going back other commit: https://github.com/archlinux/svntogit-packages/commit/94647cd1eefbdb81665c9bc9b6a0fbcee39fed1cThe config was changed, thus it might be worth you looking through the diff on the configuration and see if any of the features you wanted have been disabled, because you stated that 6.0.12-arch1-1 is working for you, thus if it is a configuration issue, the configuration changes above may show the solution to your problem.
If it is a configuration issue, one of the package maintainers will need to be contacted to request a change to the configuration file so that the mainline kernel package supports your hardware (the mainline linux package is designed to be monolithic so that it supports as much hardware as possible).
If they do not want to solve this, you will need to clone, configure and compile the linux kernel from source with the features you need enabled, you can then use:
make installwhere it will move it to the boot directory, then you need to edit your grub configuration or efi entries to boot to the new kernel, be aware this means for now on you will need to manually update every kernel update yourself.
The second solution, if the first one is not the issue, is to report this to the kernel devs as they might have changed some of the logic within this aspect of the kernel, and thus it has been broken for your hardware. Most likely I would say the first solution is the correct solution for your problem, it is the easier one :)
You may want to try linux-lts, so that you still get security patches but it should support your hardware fully. These issues you experience are the downsides of using rolling release kernel, you will run into issues like this, the lts version is designed to be reliable, so if you do not want the hassle at the expense of the latest kernel features and optimisations, switch over to lts, it still gets all the security patches just not the unstable features they are adding.
Hope this helps, Polarian
Attachment:
OpenPGP_0x0770E5312238C760.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
