-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
"Not enough context memory" on raspberry pi #522
Comments
That's obviously not right. Overflow from 32 bit size_t? |
very possible, we have stuff like this 6f1ee4b after all. |
@DiamondDemon669 What does |
on linux, you can. But I wonder if it can't be continuous. |
Are you sure? Can you point me to the Linux documentation where it says so? I am aware only of PAE and this does not raise the limitation of max size of single process memory. |
hmmm, I think I am in the wrong here. Seems like it's 4G max for a single process. |
Also, did we stop printing the system info line? It's missing from the log. |
Wasn't this only part of the |
no, ok, it's bugging out before it would print it. see example:
|
Closing as there is nothing to do here. |
you sure?, the raspi 4 is a armv8 64bit soc |
Yes, OP needs to switch to 64-bit Raspberry Pi OS and the issue will disappear. If it doesn't then we can reopen the issue. |
If that's the case, shouldn't this be detected in the build, instead of allowing it to build on 32-bit systems silently? |
Llama2 70b support
I tried loading the 7B model on a raspberry pi 4 (8GB) and it said there was not enough memory in the context pool, before segfaulting. On the raspberry pi, I am accessing the model from a hard disk on a seperate laptop, shared over sshfs, but on the laptop itself (x86 linux, 4GB RAM + 10GB swap) I access it over USB and it works perfectly fine. I am using the one before the latest versions of llama.cpp on both systems, but i changed one line of code in the raspberry pi's version. I replaced
#include <immintrin.h>
with#include <arm_neon.h>
in ggml.cWhile I was writing this I updated the raspberry pi's version of the software to the latest version and the bug still occurs. I will only disply the log from the previous version though
Log:
The text was updated successfully, but these errors were encountered: