Package Details: linux-amd-znver3 6.11.v.6-1

Git Clone URL: https://aur.archlinux.org/linux-amd-znver3.git (read-only, click to copy)
Package Base: linux-amd-znver3
Description: Linux kernel aimed at the znver3 AMD Ryzen CPU based hardware
Upstream URL: https://www.kernel.org/
Licenses: GPL2
Submitter: None
Maintainer: bebna
Last Packager: bebna
Votes: 12
Popularity: 0.30
First Submitted: 2023-05-04 15:47 (UTC)
Last Updated: 2024-11-03 03:09 (UTC)

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 Next › Last »

Anarconda commented on 2023-10-29 08:27 (UTC)

Hi, I'm really confused about the jitterentropy message. I mean, the message is gone:

┌─[09:23:34]─[amarcord@Gaia-A]
└──> ~ $ >> uname -a
Linux Gaia-A 6.5.9-AMD-znver3 #1 SMP PREEMPT_DYNAMIC Thu Oct 26 08:53:45 CEST 2023 x86_64 GNU/Linux
┌─[09:23:37]─[amarcord@Gaia-A]
└──> ~ $ >> dmesg | grep jitterentropy
┌─[✗]─[09:23:42]─[amarcord@Gaia-A]
└──> ~ $ >>

Isn't a kernel related message, then?

<deleted-account> commented on 2023-10-28 14:08 (UTC)

@iseja ty for the heads up!! rebuilds coming up.

Iseja commented on 2023-10-28 12:42 (UTC)

Please enable CONFIG_UNICODE, casefolding on ext4 needs that.

<deleted-account> commented on 2023-10-25 16:45 (UTC)

Okay well I'll commit that change regardless. I think this is a really random thing (like a race timing condition like mentioned) and its not worth losing your mind over...

Anarconda commented on 2023-10-25 16:39 (UTC)

@eggz 1. It seems I was wrong because linux-cachyos-lto 6.5.9 shows the same message. 2. ArchLinux Zen 6.5.8 doesn't 3. Your kernel whith CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE=n shows the message.

<deleted-account> commented on 2023-10-25 15:23 (UTC)

On second thought I think it might be CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE that does it. Let me fire up a build for you. (because I am going to disable it regardless)

<deleted-account> commented on 2023-10-25 15:21 (UTC)

They both have CONFIG_CRYPTO_JITTERENTROPY=yso that makes not much sense to me on first sight.

Anarconda commented on 2023-10-25 14:03 (UTC) 

By the way, I'm using other kernels eventually (cachyos-lto and ArchLinux zen version) but the message appears only with this kernel.

<deleted-account> commented on 2023-10-25 13:56 (UTC)

Interesting. While I'm sure this error is not intended and a bug indeed, since it seems to pop up pretty commonly (and popped up fairly recently), the impact is effectively zero. I'll dig in the commits if I have some spare time to see what commit might have caused this behaviour none the less as it is interesting indeed.

Anarconda commented on 2023-10-25 13:49 (UTC)

@eggz, "I assume that error does not concern this specific kernel version, because it seems to be a common error"

That is correct. I saw this error en latest kernel versions (not sure but maybe 3 or 4) but not before. I'll let it go because everything seems to be ok.

Thanks again

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 Next › Last »