Skip to content
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

detect and fix page allocation failure #3

Open
cozzyd opened this issue Jul 1, 2022 · 3 comments
Open

detect and fix page allocation failure #3

cozzyd opened this issue Jul 1, 2022 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@cozzyd
Copy link
Contributor

cozzyd commented Jul 1, 2022

spidev sometimes fails to allocate kernel memory. Solution seems to be to drop caches (e.g. echo 3 > /sys/vm/drop_caches ). Detect spidev allocation failure (inability to open spi device) and try to fix automatically? (though need permissions...)

@cozzyd cozzyd added the bug Something isn't working label Jul 1, 2022
@cozzyd cozzyd self-assigned this Jul 1, 2022
@cozzyd
Copy link
Contributor Author

cozzyd commented Jul 27, 2022

Problem likely mitigated by increasing sys.vm.min_free_kbytes to 8192. we'll see...

@cozzyd
Copy link
Contributor Author

cozzyd commented May 21, 2023

seems like not completely fixed... but not sure how to reliably detect that this is the problem rather than something else (check journalctl? that's a bit complex). Maybe rno-g-acq should do this instead if it can't open the radiant?

@cozzyd
Copy link
Contributor Author

cozzyd commented Oct 4, 2023

perhaps we need to play with fadvise? see e.g. https://stackoverflow.com/questions/3755765/what-posix-fadvise-args-for-sequential-file-write

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant