Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#65947 - linux-lts vio-pc rest BUG on kernel 5.4.* 5.5.* in VM
Attached to Project:
Arch Linux
Opened by Sebastian Münch (vfio_experte) - Monday, 23 March 2020, 11:08 GMT
Last edited by freswa (frederik) - Monday, 23 March 2020, 14:06 GMT
Opened by Sebastian Münch (vfio_experte) - Monday, 23 March 2020, 11:08 GMT
Last edited by freswa (frederik) - Monday, 23 March 2020, 14:06 GMT
|
DetailsDescription:
I have a problem with my AMD RX VEGA64 card on my KVM server. I can't not rest the VM with the vfio-pci module in the Server when booting in VM 5.4.26 or 5.5.10 kernel. it work when loading the 5.3.5-fsync kernel in VM. I have on the Server Archlinux linux-lts 5.4.26 and windows 7 and 10 works the rest with the vfio-pci moudle. I see in terminal lspci -v and the Heder of the GPU is corrupt I have stat the VM with the 5.3.5-fsync kernel and reboot the VM and boot 5.4.26 and the 5.4.26 booting correct. I reboot the VM with the 5.4.26 kernel the hang the AMD RX VEGA64 card and have afetr this BUG not header. I must rest the server complett to fix it. see the vfio3.log. Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: |
This task depends upon
Closed by freswa (frederik)
Monday, 23 March 2020, 14:06 GMT
Reason for closing: Upstream
Additional comments about closing: This doesn't seem to be a packaging issue. Please report this upstream.
Monday, 23 March 2020, 14:06 GMT
Reason for closing: Upstream
Additional comments about closing: This doesn't seem to be a packaging issue. Please report this upstream.
vfio3.log