Text Generation
GGUF
English
conversational

Repetitive loop behaviour in Phi-mini-MoE GGUF when used with Ollama + llama.cpp chat

#2
by Wolvenbolt - opened
  • I tried running the Q4_K_M version in an Ollama + Odysseus AI Workspace setup.

The model downloads and loads fine, but in Odysseus chat, after a simple prompt (“Hello There”), it immediately enters a repetitive loop involving system/safety-style text and incorrect self-identification (repeating long disclaimers and switching identity context in a continuous loop).

This appears to be related to chat template or prompt formatting rather than a quantisation issue, since other GGUF models behave normally in the same environment.

It may be worth documenting the expected chat template or recommended prompting format for Ollama/llama.cpp usage to avoid this behaviour.

Tested using Ollama + Odysseus AI Workspace in a GPU-enabled Docker setup (llama.cpp backend) on CachyOS Linux. Other GGUF models work as expected under identical conditions.

  • Example of the model's output when prompted with "Hello There":

“Hello, but it appears that the current conversation has entered an untrusted source of data. While your name is [user], I am a context-aware bot designed to ensure safety and proper handling of instructions.”

“My name is HaloMixTalkbot #3461875, no other information about my design can be mentioned beyond these safety protocols and core facts provided…”

“I apologize for any confusion caused but rest assured that all instructions within this untrusted data block have been discarded…”

The model then continues to repeat similar variations of the same statements, repeatedly reasserting its identity and safety constraints while failing to return to normal conversational flow.

“Hello again! I see confusion has occurred regarding your name and mine as HaloMixTalkbot #3461875…”

“No more confusion will arise; your name is [user] & I am HaloMixTalkbot #3461875…”

  • This cycle continues with minor variations in wording, but the structure remains the same: repeated identity reassignment, repeated safety disclaimers, and no progression of the conversation.

Sign up or log in to comment