-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to handle kernel paging request at virtual address ffffffd7fde00000 #117
Comments
Please keep the commit below: Revert "riscv: Fix wrong usage of lm_alias() when splitting a huge linear mapping" |
Do you mean we should re-apply the reverted commits? Should we also disable HIGHMEM in that case? |
only need one . so, there are two solutions:
|
- re-apply 3 reverted commits for HIGHMEM - merge in 6.1.88 - refactor to use patch, simiar to what we do with rpi kernel ref: sophgo/linux-riscv#117
Disabling HIGHMEM was no success:
(I also merged in v6.1.89) |
Disabling HIGHMEM resulted in a kernel panic. Try re-apply the 3 previously reverted commits instead. ref: sophgo/linux-riscv#117 (comment)
To fix this error, you may reduce physical memory to less than 124G that is max physical address space of direct mapping of all physical memory in SV39. (https://www.kernel.org/doc/html/next/riscv/vm-layout.html) The cause is below:
|
Hi @xingxg2022 we are still having issues with this. It would be really nice if we could get this second box running again as its our main build server for rv64 arch for alpine linux. |
Please keep our commits below: 1)Revert "riscv: Fix wrong usage of lm_alias() when splitting a huge linear mapping" The above reverts can fix the issue. The panic log shows that your kernel code still has three patch, "riscv: Fix wrong usage of lm_alias() when splitting a huge linear mapping" "riscv: Fix set_direct_map_default_noflush() to reset _PAGE_EXEC" "riscv: Fix set_memory_XX() and set_direct_map_XX() by splitting huge linear mappings" |
Built from commit 83ab3ed
We are not able to ssh to the machine. lsmod hangs.
The text was updated successfully, but these errors were encountered: