I think might have had one too many experts stripped out

#11
by Boffy - opened

Code_DzjUQWYnIt

IST Austria Distributed Algorithms and Systems Lab org

Thanks for sharing your experiment. Unfortunately, looping can occur with this model and I’ve experienced it as well. We suspect that it may be related to degraded performance at longer context lengths and this is something we’re currently working on improving in future versions.

Could you let me know at what context length you encountered the looping?

I think only had like 130k as max context and this part probably in at like 50k

You can try to switch to bf16 type for CV cache. It usually helps to reduce looping probability for Qwen family models.
Not yet representative, but yesterday I have several long sessions with this model with 128k context, bf16 keys, q8_0 value cache, without looping

I'll try with--repeat-penalty 1.05 --repeat-last-n 128 and or --dry-multiplier 0.8 if I experience this, and see if it helps.

Also, I wonder what would happen if some layers were repeated, perhaps where layers were removed.

It really seems like c# is broken on this model - it does not loop for me, but will start to hallucinate at every turn if i even mention writing c# code. for example tried several times to create c# scaffold with simple code - every time i stopped it after it produced files with mix of c#, java and c++

IST Austria Distributed Algorithms and Systems Lab org

Do you still have this problem with the updated model? Because C# is actually one of the programming languages we included in the calibration data. So I’d be happy to know if the issue still persists, as it would help us design better calibration data for future models.

the updated model, you only need to update the first large file? ie this one Qwen3.8-Flash-Next-GSQ-RCO-IQ1_M-00001-of-00002.gguf ?

IST Austria Distributed Algorithms and Systems Lab org

Yes

After some testing i still can't pinpoint exact reason for hallucinations. But i checked on 27B and it sometimes will hallucinate too.
Tried in different harness and could not reproduce. Seems like combination of harness system prompt and my prompt was the cause. C# coding is working just fine.

Sign up or log in to comment