Hi, its a strange situation, that I'm not able to understand cause there is nothing in the log, and simply, after some minutes, the system is completely locked , if I use a kernel more recent than the 5.15.xx (I can only power off with the power button).
I tried also to reinstall on a new HD (external nvm connected via USB 3.x), but nothing change also with a new installation.
I used the weekly version and all is fine and perfect... if I install the 5.15 kernel (the LTS).
This is my notebook:
I'm installing Plasma with openrc, as I use from a lot of time.
Somebody have some ideas? Thank you!
It is just a guess but the one thing that requires manual intervention with latest kernels over the "LTS" kernel is the requirement for laptop backlight options to be appended to the kernel option line of one's bootloader.
The kernel parameters:
acpi_backlight=video
acpi_backlight=vendor
acpi_backlight=native
One of these three options may do the trick.
jspaces, are you talking about to add these parameters to the grub.cfg?
@jspaces no one of that parameters work: the system, with kernel newer than 5.15 go in lock. I reinstalled all from the ground on a new disk, just to eliminate any other questions and nothing change. :'(
Could you post the kernel log please. Clear it first. Then boot, wait for crash, boot back in and get the log. Post it all.
If you have another system, local or vps, running 24/7 setting up remote logging may show some information which is lost when the system crashes. How you go about it depends on what provides logging on both the local and remote system but there's plenty of tutorials if you do try this. My only experience of this was from rsyslog -> syslog-ng and it was past trivial but by no means really hard to set up.
Other than that you could try getting a list of modules your running kernel is using then experimenting with blacklisting them one by one (or in groups where related). Obviously you'll lose functionality and may even end up with a non-booting system but so long as you know how to chroot in or similar you can revert the changes.
This might help narrow down what is causing the issue?
Sorry it was just a shot in the dark without any information on the specifics of your setup.
@jspaces: thanks' for your info, I know that its a black hole; today I investigated and I discover that its a problem also of other users, but I wasn't able to find a solution. I'll continue to investigate some days and after I'll open a bug with the kernel people. What happen is really very strange: something is changed into the kernel!
@gripped : tomorrow I'll try to send a kernel log before and after, but I think that nothing is registered, all is in lock, no way to do nothing TTY1, sysreq... nothing :-) but I'll do, maybe an idea. I cannot connect another PC remotely, I think that the engineering, working in my office, wont be so happy if I reinstall one of their Autocad workstation to investigate my bug ahahahah I risk to finish in a concrete wall ahahahahah
I got a good laugh. :)
I remember earlier Autodesk licences being nasty to deal with when things go south with their liking of putting stuff into the so-called empty spaces of MBR partition tables.
You could try turning off graphics hardware acceleration things, in the desktop, in your browser if you are using one while the problem happens, and even try booting with nomodeset on the commandline to see if it is graphics related, as that's a common cause of lockups, which might help narrow down the cause slightly.
I'm almost sure that all is solved and, simply, upgrading the BIOS Firmware. Yesterday I compiled a checklist of all the possible component able to create a similar problem and... nobody of them, in my opinion, was significant. At the end of the list there was also the bios upgrade; I was sure that some months ago I applied the upgrade, but it was for another notebook and not for this one. Done and all is working perfectly (till now...) ;D
The only thing that I can tell is that Tuxedo, together with the bios upgrade, always available on the web site, can do 2 important things:
1) to advice the user that there is a bios upgrade available; might be with a mail?
2) to compile a Readme.txt or something similar, to explain what the bios upgrading is implementing.
Regards and thank you for your support.