PessimistTech

@ravenet Sure, gave that a whirl and no change, though I did notice some nvtop weirdness as it would show some load, but most of the wait time there was actually no load on the GPUs instead of the constant load matching the model being loaded. For some historical context ARI support was initially disabled in the bios when I started this thread. That was on the list of things I enabled when I started seeing some success with ollama (something in the changes since has broken ollama now too, but there was at least some forward progress after enabling). dmesg output overall looked the same, but I did see this output on the console (and in dmesg) that seemed interesting. Not 100% sure at this point if this was in the previous dmesg outputs or not, but may be worth sharing. EDIT: looks like this may actually be new... I looked back through the past dm dmesg outputs and I did not see this output.

[  108.547683] amdgpu 0000:00:09.0: MES(0) failed to respond to msg=REMOVE_QUEUE
[  108.547729] amdgpu 0000:00:09.0: failed to remove hardware queue from MES, doorbell=0x1202
[  108.547746] amdgpu 0000:00:09.0: MES might be in unrecoverable state, issue a GPU reset
[  108.547774] amdgpu 0000:00:09.0: Failed to evict queue 2
[  108.547789] amdgpu 0000:00:09.0: Failed to evict process queues
[  108.547803] amdgpu: Failed to quiesce KFD
[  108.547870] amdgpu 0000:00:09.0: GPU reset begin!. Source:  3
[  109.656850] amdgpu 0000:00:09.0: Failed to remove queue 0
[  109.657324] amdgpu 0000:00:09.0: Dumping IP State
[  109.756265] amdgpu 0000:00:09.0: Dumping IP State Completed
[  112.047695] amdgpu 0000:00:09.0: MODE1 reset
[  112.047797] amdgpu 0000:00:09.0: GPU mode1 reset
[  112.054505] amdgpu 0000:00:09.0: GPU smu mode1 reset
[  113.075393] amdgpu 0000:00:09.0: GPU reset succeeded, trying to resume
[  113.090354] amdgpu 0000:00:09.0: [drm] PCIE GART of 512M enabled (table at 0x00000087D6B00000).
[  113.092905] amdgpu 0000:00:09.0: [drm] AMDGPU device coredump file has been created
[  113.092913] amdgpu 0000:00:09.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[  113.092917] amdgpu 0000:00:09.0: VRAM is lost due to GPU reset!
[  113.092921] amdgpu 0000:00:09.0: PSP is resuming...
[  114.997591] amdgpu 0000:00:09.0: GECC is disabled, set amdgpu_ras_enable=1 to enable GECC in next boot cycle if needed
[  115.091125] amdgpu 0000:00:09.0: RAP: optional rap ta ucode is not available
[  115.091130] amdgpu 0000:00:09.0: SECUREDISPLAY: optional securedisplay ta ucode is not available
[  115.091134] amdgpu 0000:00:09.0: SMU is resuming...
[  115.091375] amdgpu 0000:00:09.0: smu driver if version = 0x0000002e, smu fw if version = 0x00000033, smu fw program = 0, smu fw version = 0x00684c00 (104.76.0)
[  115.432371] amdgpu 0000:00:09.0: SMU is resumed successfully!
[  115.445556] amdgpu 0000:00:09.0: program CP_MES_CNTL : 0x4000000
[  115.445731] amdgpu 0000:00:09.0: program CP_MES_CNTL : 0xc000000
[  115.750240] amdgpu 0000:00:09.0: [drm] DMUB hardware initialized: version=0x0A000800

As an update for other things I have tried, in order to eliminate hardware issues, or bios settings I tried installing proxmox and spinning up a VM there with both GPUs passed through and it worked just fine... With that feedback I did a fresh install of XCP-NG 8.3 and spun up a fresh VM using the same steps as I used on proxmox and still no dice. This leads me to believe the issue is somewhere in the XCP-NG passthrough stack with my specific hardware...

@ravenet well... thanks for the idea. I went ahead and tried spinning up an opensuse slowroll VM. I installed docker and the amdgpu firmware/kernel drivers, and tried running lemonade-server and ollama and same behavior. So that definitely seems to point to something weird going on on my host rather than the guest software stack...

@TeddyAstie Is this specific to the lack of interrupts?

for future reference here is the xl dmesg at this point
xldmesg.txt

@ravenet welp, removed the amdgpu.msi=0 option, and I am seeing 0 interrupts in the /proc/interrupts file, and overall behavior is still the same...

106:          0          0          0          0          0          0  xen-pirq    -msi       amdgpu

@ravenet ooh, thanks for the callout, that is a config that is left over from some earlier debugging. I'll remove that and try again.

I had a similar thought about the model size of the qwen 3.6 model (chosen intially for running on both GPUs). I also tested with llama3.2 for a much smaller test.

@ravenet
Thanks for the ideas!

Here's the outcome of the tests
ps -eo pid,stat,wchan:32,cmd | grep llama:

62 Rl   -                                /root/.cache/lemonade/bin/llamacpp/rocm-nightly/llama-server -m /root/.cache/huggingface/hub/models--unsloth--Qwen3.6-35B-A3B-GGUF/snapshots/a483e9e6cbd595906af30beda3187c2663a1118c/Qwen3.6-35B-A3B-UD-Q4_K_XL.gguf --ctx-size 262144 --port 8001 --jinja --metrics --mmproj /root/.cache/huggingface/hub/models--unsloth--Qwen3.6-35B-A3B-GGUF/snapshots/a483e9e6cbd595906af30beda3187c2663a1118c/mmproj-F16.gguf --reasoning-format auto --no-webui --temp 1.0 --top-p 0.95 --top-k 20 --min-p 0.00 --repeat-penalty 1.0 --chat-template-kwargs {"preserve_thinking":true}

sudo dmesg -w | grep -iE "amdgpu|sdma|ring|fence":
dmesgout.txt

Same overall results... I even re-ran the same tests after removing the 2nd GPU from the PCI passthrough settings and still the same...

I also seem to run into an issue where the GPU tends to get stuck after some of these tests. Even rebooting gets stuck waiting for llama server processes to stop and I end up having to force power off. Not sure if that is related as I get the same output on the first test, but it may be worth noting.

@ravenet well, applied those updates and still the same results unfortunately...

I am definitely seeing load on the GPU, so it is able to start the process, lemonade server just sits waiting logging
2026-07-08 20:06:06.477 [Debug] (WrappedServer) Still waiting for llama-server...
while the GPUs are sitting there with the model in mem (or at least the correct amount of mem for the model size being consumed).

looks like the rocm backend is using version b1292 which does note the correct gfx1201 model in the release notes.

@ravenet I have not tried with the rocm backend yet, but I will give that a whirl. When using the GPUs it never completes the model load.

For testing I was just using the docker run command from the lemonade server docs.

docker run -d \
	--name lemonade-server \
	-p 13305:13305 \
	-v lemonade-cache:/root/.cache/huggingface \
	-v lemonade-llama:/opt/lemonade/llama \
	-v lemonade-recipe:/root/.cache/lemonade \
	--device=/dev/kfd \
	--device=/dev/dri \
	ghcr.io/lemonade-sdk/lemonade-server:latest

Command output:

lspci -vv -s 00:08.0 | grep -E "Region [0-9]|LnkSta:"
	Region 0: Memory at 1000000000 (64-bit, prefetchable) [size=32G]
	Region 2: Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at c300 [size=256]
	Region 5: Memory at e0800000 (32-bit, non-prefetchable) [size=512K]
		LnkSta:	Speed 32GT/s, Width x16

lspci -vv -s 00:08.0 | grep -iE AtomicOP
			 AtomicOpsCap: 32bit+ 64bit+ 128bitCAS-
			 AtomicOpsCtl: ReqEn+

@ravenet sure, the workloads I have been testing with include ollama, vLLM, and lemonade server (all via docker for easier setup, but I do have all the rocm/AMD drivers and what not setup on the VM directly). Ollama works just fine now, but lemonade server still hangs and vLLM fails with the same errors on startup.

Cool, thanks for info/checking!