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

perplexity assert fails #6246

Closed
jart opened this issue Mar 22, 2024 · 1 comment · Fixed by #6122
Closed

perplexity assert fails #6246

jart opened this issue Mar 22, 2024 · 1 comment · Fixed by #6122

Comments

@jart
Copy link
Contributor

jart commented Mar 22, 2024

If I run perplexity as follows:

./perplexity -m ~/weights/mistral-7b-instruct-v0.2.Q5_K_M.gguf -f ~/vendor/wiki.test.raw -s 31337

I get an assertion failure on the logits_valid array.

perplexity: tokenizing the input ..
perplexity: tokenization took 546.595 ms
perplexity: calculating perplexity over 642 chunks, n_ctx=512, batch_size=2048, n_seq=4
ggml_gallocr_needs_realloc: graph has different number of nodes
ggml_gallocr_alloc_graph: cannot reallocate multi buffer graph automatically, call reserve
ggml_backend_sched_alloc_splits: failed to allocate graph, reserving
ggml_gallocr_needs_realloc: node CUDA0#k-0#0 is not valid
ggml_gallocr_alloc_graph: cannot reallocate multi buffer graph automatically, call reserve
ggml_backend_sched_alloc_splits: failed to allocate graph, reserving
ggml_gallocr_needs_realloc: node CUDA0#k-0#0 is not valid
ggml_gallocr_alloc_graph: cannot reallocate multi buffer graph automatically, call reserve
ggml_backend_sched_alloc_splits: failed to allocate graph, reserving
ggml_gallocr_needs_realloc: node CUDA0#k-0#0 is not valid
ggml_gallocr_alloc_graph: cannot reallocate multi buffer graph automatically, call reserve
ggml_backend_sched_alloc_splits: failed to allocate graph, reserving
perplexity: 2.44 seconds per pass - ETA 6.50 minutes
perplexity: llama.cpp:14296: float* llama_get_logits_ith(llama_context*, int32_t): Assertion `ctx->logits_valid.at(i)' failed.
Aborted (core dumped)
@slaren
Copy link
Collaborator

slaren commented Mar 22, 2024

It's an innocuous error, will be fixed in #6122.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants