What is that value for the second Athlon core (seems extremely bogus), and
would/could that be the reason for the schedule_timeouts? This bogus value
also shows up in the bootup log when the second core is activated. Seems to
be AMD specific, as the values are correct on my Xeon machines.
That's a 32bit machine I assume.
Yes. This was decoded recently as an issue on 32bit due to a calculation
which is based on 'unsigned long' but requires to be 64bit wide.
It's in the 4.18.8 stable kernel, which should be available from your
fedora repo anytime soon.