Bug 212917
Summary: | Unable to handle kernel NULL pointer dereference at virtual address | ||
---|---|---|---|
Product: | Memory Management | Reporter: | rudi |
Component: | Other | Assignee: | Andrew Morton (akpm) |
Status: | NEW --- | ||
Severity: | normal | CC: | rudi, stefan.bruens |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.12 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
rudi
2021-05-01 11:12:36 UTC
The OS itself is a patched Ubuntu 20.04.2 I see the same, but also all other kinds of memory errors, like userspace segfaults, "stack smashing" faults, etc. When I run with kernel command line parameter maxcpus=4, i.e. disabling the two A72 cores, the systems runs fine even under stress. Offlining the two A72 cores via sysfs has the same effect, enabling the cores again makes the system unreliable. This is completely repeatable. I believe that this has been addressed in 5.13, I read the patch somewhere About adjusting 1 to 2 or 2 to 1… I just can’t find the reference at the moment. Closing the bug. I believe this has contributed to the fix - https://lore.kernel.org/lkml/20210511211335.2935163-1-pgwipeout@gmail.com/ Along with the DTS - https://lore.kernel.org/lkml/20210527105943.GA441@7698f5da3a10/ - https://lore.kernel.org/lkml/20210527122911.GA1640@7698f5da3a10/ |