Hello Kowshik, thanks for the verification, even if the result is not
like expected :-/
I double checked if the patch is properly included:
~/ubuntu-noble-master-next/noble-clean$ git log --oneline --grep
"powerpc/64s/radix/kfence: map __kfence_pool at page granularity"
ec65624fc069 powerpc/64s/radix/kfence: map __kfence_pool at page granularity
~/ubuntu-noble-master-next/noble-clean$ git tag --contains ec65624fc069
Ubuntu-6.8.0-48.48
And it is.
And we have currently set CONFIG_KFENCE to yes for all architectures, incl.
ppc64el:
grep -ri CONFIG_KFENCE\ debian.master/*
debian.master/config/annotations:CONFIG_KFENCE
policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64':
'y', 's390x': 'y'}>
Oh dear, so that is (according to the Ubuntu SRU terms) first of all a
"verification-failed".
Either the proposed fix (to cherry-pick "powerpc/64s/radix/kfence: map
__kfence_pool at page granularity") is either not fixing the situation like
expected, or there is more needed (like for example setting CONFIG_KFENCE to
'n' for ppc64el only)?!
Is a new root cause analysis for this issue needed?
And shall we pull the commit again out of the Ubuntu kernel (which is tricky,
since we are already late in the SRU cycle)?
@IBM what do you think?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060039
Title:
[Ubuntu-24.04] FADump with recommended crash size is making the L1
hang
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2060039/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
