Skip to content

Eval bug: --no-kv-offload causes immediate EOS generation with Qwen3.6-27B on Vulkan (works without flag) #24519

Description

@Dam14n

Name and Version

llama-server --version
build 9608 (70b54e1)

Operating systems

Windows

GGML backends

Vulkan

Hardware

  • 2x AMD Radeon RX 6700 XT
  • 64 GB RAM
  • Ryzen 5950X 16T

Models

Qwen3.6-27B-UD-Q4_K_XL.gguf

Problem description & steps to reproduce

When running llama-server with --no-kv-offload, the model immediately terminates generation by predicting EOS as the first generated token.

The same model, prompt, and server configuration work correctly when --no-kv-offload is removed.

Working Command

llama-server \
  -m ./Qwen3.6-27B-UD-Q4_K_XL.gguf \
  --port 1234 \
  -ngl 999

Generation works normally and returns text.

Relevant log:

CPU KV buffer size = 0.00 MiB

Failing Command

llama-server \
  -m ./Qwen3.6-27B-UD-Q4_K_XL.gguf \
  --port 1234 \
  -ngl 999 \
  --no-kv-offload

Generation produces no text.

Relevant logs:

CPU KV buffer size = 4000.00 MiB

and

predicted_n = 1
stop_type = "eos"
ignore_eos = false

The model immediately predicts EOS as the first generated token.

Expected Behavior

The model should generate text normally regardless of whether the KV cache is stored on GPU or CPU.

Actual Behavior

Prompt evaluation succeeds, but generation immediately stops with EOS before any text is produced.

Minimal Reproduction

Works:

llama-server -m ./Qwen3.6-27B-UD-Q4_K_XL.gguf -ngl 999

Fails:

llama-server -m ./Qwen3.6-27B-UD-Q4_K_XL.gguf -ngl 999 --no-kv-offload

First Bad Commit

No response

Relevant log output

Logs

WORKING LOGS.txt

NOT WORKING LOGS.txt

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions