System crash related to sof-audio?

nxe9 · Tux's lil' helper Joined: 05 Jun 2021 Posts: 115

Hi, I have a strange system crash on my thinkpad. I have a newly installed system. There's not much on it yet. The system boots up without a problem, then I log in as root and nothing happens for the first few minutes. After a while, dmesg output automatically appears in the terminal. Looks like there was a crash. I can continue to use the system. However, I cannot turn off or reset the computer using the command. I have to do it physically.

Kernel: gentoo-kernel 6.6.58-r1 the stable one. I am currently installing the 6.11.8 and I will tell you if the problem appears in the latest version.

Dmesg Log https://bpa.st/7T5A

nxe9 · Tux's lil' helper Joined: 05 Jun 2021 Posts: 115

sys-kernel/gentoo-kernel 6.11.8 solved my problem.

It sounds it is a bad idea to use 6.6 with the newest thinkpad. Looking through information on the internet, 6.6 has various problems with my hardware.
- Graphic is unstable
- Some bugs regarding wifi

Also, now let's add my problem that I had here in the thread.

Another question, what is the method to install the latest kernel or more general the latest package? I added sys-kernel/gentoo-kernel ~amd64 into package.accept_kernel and it didn't work. I found on the internet that I need to add virtual/dist-kernel ~amd64 as well. Now it works and I can install the latest package. But how would I know that? Do I need to analyze the dependency tree somehow? I would expect that adding just gentoo-kernel would be enough. And if that wasn't enough, I would expect portage to inform me about it itself. However, this was not happening. My question now concerns portage rather than kernel, sorry

.

Hu · Administrator Joined: 06 Mar 2007 Posts: 22673

Adding sys-kernel/gentoo-kernel to your /etc/portage/package.accept_keywords should have been sufficient to allow Portage to install a testing version of that package, if you asked for that package or asked for a package that depended on it. Did you? You did not show the command you ran or its output (as requested in Guidelines item #4), so we can only guess at why Portage did not do what you want. If I were to guess, you tried to (re)install the stable version of virtual/dist-kernel, and the virtual that you (re)installed is locked to depend on kernels from the same major line, so installing '=virtual/dist-kernel-6.6*' can only ever request to install '=sys-kernel/gentoo-kernel-6.6*'. If you had directly requested sys-kernel/gentoo-kernel, Portage probably would have given you a testing version of it.

nxe9 · Tux's lil' helper Joined: 05 Jun 2021 Posts: 115

@Hu:

1. package.accept_keywords doesn't contain changes

2.

Hu · Administrator Joined: 06 Mar 2007 Posts: 22673

I did not review sys-kernel/gentoo-kernel before my prior post. I checked that now, and see that it has a PDEPEND on a version-matched dist-kernel. Therefore, I suspect that when you had testing gentoo-kernel and stable dist-kernel, Portage started down the path of using testing gentoo-kernel, noticed that it could not get a matching dist-kernel, and backtracked to the stable series. That was a valid solution (albeit not the one you wanted), so Portage showed that, and did not mention that it had abandoned the path using a testing gentoo-kernel. It is normal for Portage not to report failed paths if it can find a successful one.

Using emerge --pretend --verbose '=sys-kernel/gentoo-kernel-6.11*' might have produced the answer more directly, since that would force Portage to use that series or explain why not, without allowing it to backtrack down to the 6.6 series. If dist-kernel was not keyworded, the request would have failed, but it would have failed with a nice error message.