Open one-lithe-rune opened 1 year ago
I can reproduce this on my nvidia turing card as well so is most likely happening across all platforms
I believe the immediate cause is that the pipeline code path sets up the schedulers for the selected model stablediffusion-2-1
before it gets to these lines which switch over to stablediffusion-2-1-base
:
...the CPU schedulers therefore remain setup for 2.1 and therefore their config suddenly becomes incorrect.
When I tried just taking out those workaround lines a week or so back, that just left things in a different broken state, so presumably stablediffusion-2-1 is still not working with the code otherwise as is.
SharkEulerDiscrete working is a bit of mystery. Perhaps it would become broken if 2.1 was working and the workaround was removed. Dunno.
If I use any scheduler other than SharkEulerDiscrete with the stablediffusion-2-1 model I get flat beige images (with some variation in shade of beige across the image).
I see this with both 648 and 693, and with both the default target triple for my card (Radeon VII)
rdna2-unknown-windows
and with thergcn5-radeonvii-windows
target triple (which might be more correct?).This doesn't occur with stablediffusion-2-1-base in 693. I haven't tested this with that model in 648.
If I do use SharkEulerDiscrete I get normal looking images generated.
Drivers are Adrenalin 23.3.2, and I have AMD_ENABLE_LLPC=1 set in my envars.