Issues with UD-Q2_K_XL quant

#9
by labhraighlep - opened

I was comparing some of these quants for quality and started with the lm-eval repo, the GSM8K bench specifically.
Ran to completion at 95% for the UD-IQ_4_NL and UD-Q4_K_S quants.
The UD-Q2_K_XL quant went into a runaway generation looping on decode at 37/1319 on 5 consecutive runs, always at the same spot. Reasoning was disabled. Ran the one shots for 36,37,38 separately, successfully but it failed out on the full test every time. Also tested limiting max_gen_toks.

Are there issues with this quant?

Just stopping by to say I noticed this as well, but I noticed it on a separate users Q2 quant... Some opencode sessions passed without a problem, even 100k+ context in, and others had this run on issue. It seemed to occur in the same spot. even after re-prompting from 0. Very annoying when it happens in a high context session.

I assume it was a run on generation loop because one of my 3 GPUS would peg at 100% and the others would idle. I have since grabbed a Q4 quant, and so far, although slower PP, haven't had this issue.

I have the same issue with UD-Q3_K_XL.... A prompt a bit more complex... And the model goes to an endless reasoning... Unfortunately, my setup doesn't handle higher quants.... :-(

@Chico70 - user @sokann has a great 2bit quant of GLM 5.2, and I got it to convert an entire .NET 3.5 codebase into a .NET 8.0 codebase. App now has cross compatibility and functions as the original version did. Might want to check that one out! I ran it over the course of 4 days, some sessions were 8+ hours and it worked GREAT.

@chiko70
The GLM-5.2-GGUF/UD-IQ2_M version does not have this issue. I'm going to test the GLM-5.2-GGUF/UD-IQ1_M VERSION too to see if it is consistent. I'll test the UD-IQ3_S too because it falls under the size of the UD-Q3_K_KL you are seeing issues with. I'm doing this as part of my own effort to expand my abilities to be able to test quants.

I'm using the GSM8K benchmarks testing the looping running through all 3139 tests,

Sign up or log in to comment