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

Eval bug: context shift is disabled #11974

Open
deific opened this issue Feb 20, 2025 · 2 comments
Open

Eval bug: context shift is disabled #11974

deific opened this issue Feb 20, 2025 · 2 comments

Comments

@deific
Copy link

deific commented Feb 20, 2025

Name and Version

./llama.cpp/build/bin/llama-server  \
  -m /models/DeepSeek-R1-UD-IQ1_S-00001-of-00003.gguf \
  --cache-type-k q4_0 \
  --threads 64 \
  --temp 0.6 \
  --ctx-size 12288 \
  --parallel 3 \
  --n-gpu-layers 62 

Operating systems

Linux

GGML backends

BLAS

Hardware

AMD EPYC 9754 128-Core Processor
8 * RTX 4090D 24G

Models

DeepSeek-R1-UD-IQ1_S

Problem description & steps to reproduce

Error message after multiple rounds of conversation: context shift is disabled。

First Bad Commit

No response

Relevant log output

slot launch_slot_: id  1 | task 4640 | processing task
slot update_slots: id  1 | task 4640 | new prompt, n_ctx_slot = 4096, n_keep = 0, n_prompt_tokens = 3844
slot update_slots: id  1 | task 4640 | kv cache rm [3798, end)
slot update_slots: id  1 | task 4640 | prompt processing progress, n_past = 3844, n_tokens = 46, progress = 0.011967
slot update_slots: id  1 | task 4640 | prompt done, n_past = 3844, n_tokens = 46
slot      release: id  1 | task 4640 | stop processing: n_past = 4095, truncated = 0
srv    send_error: task id = 4640, error: context shift is disabled
srv  update_slots: no tokens to decode
srv  update_slots: all slots are idle
srv  cancel_tasks: cancel task, id_task = 4640
srv  update_slots: all slots are idle
srv  log_server_r: request: POST /v1/chat/completions 127.0.0.1 200
@zshihang213
Copy link

I got the same error 'context shift is disabled' after a few rounds with --ctx-size 2048. Maybe the history is too long for the ctx-size?

@grimulkan
Copy link

#7343 is what is going on I think

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

No branches or pull requests

3 participants