Recent content by dcsapak

fyi: if you need a history of those docs, you can see older versions directly in git: https://git.proxmox.com/?p=pve-docs.git;a=summary

this was a wrong/incomplete backport it seems and was fixed a few days ago: https://git.proxmox.com/?p=pve-kernel.git;a=commit;h=2892a0d2a69c915c398e9e91580e6ad81f11c951 and should be fixed with 7.0.14-26 yes this should be fine usually we provide some (critical) fixes for a while, but aside...

Hi, this sounds like the "famous" radeon reset bug, but did you try with older kernel versions (to test for regressions). at least to me it isn't a known issue. That said, passing through (on) consumer hardware is always a bit of a gamble, especially so with integrated devices and is often...

hi, no, the list just represents the versions explicitely tested in our lab In general newer versions of the driver also work on the tested kernel (minor versions). kernel patch versions are in general also compatible (except some security fixes might need adaption of some interface, but this...

hi, can you provide more information please? the output of dmesg, the journal, the vm config as well as the iommu groups would be interesting, thanks!

is there any more information in the syslog/journal during that time? a timeout of 'query-backup' can have many sources. is the vm itself fine?

yeah i also agree, currently working on a way to visualize this differently, but no time frame yet ;)

hi, this should be fixed (since a while) at least in 7.0.14-14 exceprt from 'apt changelog proxmox-kernel-7.0'

thanks for the writeup ! since we don't have such a card here to test and/or verify, you could file your findings in the upstream kernel bugzilla ;)

it would entail installing an upstream kernel, best on a test machine and if it's still the upstream behavior open a bug on https://bugzilla.kernel.org/ i don't have a a580 to test here at the moment so I can't do the test myself sadly

mhmm the only thing that stands out is that ASPM L1 is enabled on the working system while not on the not working one. between those kernels there are only a few ASPM related changes, and only one is generic: https://lore.kernel.org/all/20260428040104.78524-1-carlos.bilbao@kernel.org/ not sure...

can you also attach a lspci output from a bad kernel? EDIT: also please run lspci as root, otherwise some information is not visible there (such as the capabilities, etc.)

i forwarded this internally, not sure if we want to go against upstream here since the vfio-pci binding works already (and is recommended for passthrough anyway) if you can reproduce with the upstream kernel, i'd report it on the official kernel bugzilla too

mhmm could you also check the -17, -18 and -19 kernels? this would shrink the possible regression window by a lot from a good and a bad boot the following output would also be practical: lspci -PP -vvv

can you try to turn off aspm for the device? e.g. via the kernel commandline: `amdgpu.aspm=0` EDIT: or try to bind the card to vfio-pci before amdgpu with a vfio-pci.ids=<ids> (and maybe a softdep) see https://pve.proxmox.com/pve-docs/chapter-qm.html#_host_configuration