cancel
Showing results for 
Search instead for 
Did you mean: 

Graphics

rhyzom
Journeyman III

Scrambled screen, disconnected keyboard, xen 4.14, debian 10, AMD RX 550

Sorry, I'm not a mother tongue.

I'm trying to get xen running with debian 10. debian 10 comes up, xen-tools tell me about the diskimages. Looks fine to me.

Not fine looks the way xen/debian stubbornly each time comes back from sleep. I know the problems with freeze on suspend (may be its the MSI X370 Carbon Pro Gaming AC mainboard), so the powersaving states are deactivated in UEFI.

After the wake-up call the screen comes back with xscreensavers login window. After the credentials I get the working screen but scrambled, disturbed, zoomed, wrong colours.

Login-in from another machine to restart lightdm.service, the screen goes black (looks good), the debian login-in window comes up (ok) but then, the same disrupted screen is shown.

Also looks, like the keyboard is not recognized any more. The mouse moves on the garbled screen but nothing is to be seen if I try to insert text into a writer window.

-- Logs begin at Sat 2020-08-15 18:40:41 CEST, end at Wed 2020-12-16 15:04:07 CET. --
Dez 15 17:08:32 machine kernel: Linux version 5.9.0-4-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.0-19) 10.2.0, GNU ld (GNU
Dez 15 17:08:32 machine kernel: Command line: placeholder root=UUID=b2e8a721-7426-4161-ad7e-628944720b45 ro quiet
Dez 15 17:08:32 machine kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Dez 15 17:08:32 machine kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Dez 15 17:08:32 machine kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Dez 15 17:08:32 machine kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Dez 15 17:08:32 machine kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Dez 15 17:08:32 machine kernel: Released 0 page(s)
Dez 15 17:08:32 machine kernel: BIOS-provided physical RAM map:
Dez 15 17:08:32 machine kernel: Xen: [mem 0x0000000000000000-0x000000000009ffff] usable
Dez 15 17:08:32 machine kernel: Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Dez 15 17:08:32 machine kernel: Xen: [mem 0x0000000000100000-0x0000000009d7ffff] usable
Dez 15 17:08:32 machine kernel: Xen: [mem 0x0000000009d80000-0x0000000009ffffff] reserved
Dez 15 17:08:32 machine kernel: Xen: [mem 0x000000000a000000-0x000000000a1fffff] usable
Dez 15 17:08:32 machine kernel: Xen: [mem 0x000000000a200000-0x000000000a20afff] ACPI NVS
Dez 15 17:08:32 machine kernel: Xen: [mem 0x000000000a20b000-0x000000000affffff] usable
Dez 15 17:08:32 machine kernel: Xen: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Dez 15 17:08:32 machine kernel: Xen: [mem 0x000000000b020000-0x00000000db6e9fff] usable
Dez 15 17:08:32 machine kernel: Xen: [mem 0x00000000db6ea000-0x00000000db859fff] reserved
Dez 15 17:08:32 machine kernel: Xen: [mem 0x00000000db85a000-0x00000000dbcdbfff] usable
Dez 15 17:08:32 machine kernel: Xen: [mem 0x00000000dbcdc000-0x00000000dbdf2fff] ACPI NVS
Dez 15 17:08:32 machine kernel: Xen: [mem 0x00000000dbdf3000-0x00000000dcf99fff] reserved
Dez 15 17:08:32 machine kernel: Xen: [mem 0x00000000dcf9a000-0x00000000deffffff] usable
Dez 15 17:08:32 machine kernel: Xen: [mem 0x00000000df000000-0x00000000dfffffff] reserved
Dez 15 17:08:32 machine kernel: Xen: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Dez 15 17:08:32 machine kernel: Xen: [mem 0x00000000fd000000-0x00000000ffffffff] reserved
Dez 15 17:08:32 machine kernel: Xen: [mem 0x0000000100000000-0x000000081f37ffff] usable
Dez 15 17:08:32 machine kernel: Xen: [mem 0x000000fd00000000-0x000000ffffffffff] reserved
Dez 15 17:08:32 machine kernel: NX (Execute Disable) protection: active
Dez 15 17:08:32 machine kernel: efi: EFI v2.70 by American Megatrends
Dez 15 17:08:32 machine kernel: efi: ACPI 2.0=0xdbd6f000 ACPI=0xdbd6f000 SMBIOS=0xdcde5000 MEMATTR=0xd983e018 ESRT=0xd9842f98 
Dez 15 17:08:32 machine kernel: secureboot: Secure boot disabled
Dez 15 17:08:32 machine kernel: SMBIOS 2.8 present.
Dez 15 17:08:32 machine kernel: DMI: Micro-Star International Co., Ltd. MS-7A32/X370 GAMING PRO CARBON AC (MS-7A32), BIOS 2.IR 07/06/2020
Dez 15 17:08:32 machine kernel: Hypervisor detected: Xen PV
Dez 15 17:08:32 machine kernel: tsc: Fast TSC calibration using PIT
Dez 15 17:08:32 machine kernel: tsc: Detected 3400.186 MHz processor
Dez 15 17:08:32 machine kernel: tsc: Detected 3400.062 MHz TSC
Dez 15 17:08:32 machine kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Dez 15 17:08:32 machine kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Dez 15 17:08:32 machine kernel: last_pfn = 0x81f380 max_arch_pfn = 0x400000000
Dez 15 17:08:32 machine kernel: Disabled
Dez 15 17:08:32 machine kernel: x86/PAT: MTRRs disabled, skipping PAT initialization too.
Dez 15 17:08:32 machine kernel: x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WC  WP  UC  UC  
Dez 15 17:08:32 machine kernel: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
Dez 15 17:08:32 machine kernel: RAMDISK: [mem 0x04000000-0x07ca1fff]
Dez 15 17:08:32 machine kernel: ACPI: Early table checksum verification disabled
Dez 15 17:08:32 machine kernel: ACPI: RSDP 0x00000000DBD6F000 000024 (v02 ALASKA)
Dez 15 17:08:32 machine kernel: ACPI: XSDT 0x00000000DBD6F0A0 0000BC (v01 ALASKA A M I    01072009 AMI  00010013)
Dez 15 17:08:32 machine kernel: ACPI: FACP 0x00000000DBD76C80 000114 (v06 ALASKA A M I    01072009 AMI  00010013)
Dez 15 17:08:32 machine kernel: ACPI: DSDT 0x00000000DBD6F1F0 007A8E (v02 ALASKA A M I    01072009 INTL 20120913)
Dez 15 17:08:32 machine kernel: ACPI: FACS 0x00000000DBDDBE00 000040
Dez 15 17:08:32 machine kernel: ACPI: APIC 0x00000000DBD76D98 00015E (v03 ALASKA A M I    01072009 AMI  00010013)
Dez 15 17:08:32 machine kernel: ACPI: FPDT 0x00000000DBD76EF8 000044 (v01 ALASKA A M I    01072009 AMI  00010013)
Dez 15 17:08:32 machine kernel: ACPI: FIDT 0x00000000DBD76F40 00009C (v01 ALASKA A M I    01072009 AMI  00010013)
Dez 15 17:08:32 machine kernel: ACPI: SSDT 0x00000000DBD76FE0 0000FC (v02 ALASKA CPUSSDT  01072009 AMI  01072009)
Dez 15 17:08:32 machine kernel: ACPI: SSDT 0x00000000DBD770E0 008C98 (v02 AMD    AMD ALIB 00000002 MSFT 04000000)
Dez 15 17:08:32 machine kernel: ACPI: SSDT 0x00000000DBD7FD78 003776 (v01 AMD    AMD AOD  00000001 INTL 20120913)
Dez 15 17:08:32 machine kernel: ACPI: MCFG 0x00000000DBD834F0 00003C (v01 ALASKA A M I    01072009 MSFT 00010013)
Dez 15 17:08:32 machine kernel: ACPI: HPET 0x00000000DBD83530 000038 (v01 ALASKA A M I    01072009 AMI  00000005)
Dez 15 17:08:32 machine kernel: ACPI: SSDT 0x00000000DBD83568 000024 (v01 AMDFCH FCHZP    00001000 INTL 20120913)
...skipping...
Dez 16 09:47:23 machine avahi-daemon[1196]: Interface eno1.IPv6 no longer relevant for mDNS.
Dez 16 09:47:23 machine NetworkManager[1189]: <info>  [1608108443.6846] manager: NetworkManager state is now CONNECTED_GLOBAL
Dez 16 09:47:23 machine NetworkManager[1189]: <info>  [1608108443.7143] manager: NetworkManager state is now DISCONNECTED
Dez 16 09:47:23 machine NetworkManager[1189]: <info>  [1608108443.7154] device (eno1): state change: unmanaged -> unavailable (reason 'mana
Dez 16 09:47:23 machine dbus-daemon[1183]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.fre
Dez 16 09:47:23 machine dbus-daemon[1183]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dez 16 09:47:25 machine audit[15819]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15819 comm="cups-brows
Dez 16 09:47:25 machine kernel: audit: type=1400 audit(1608108445.535:90): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-br
Dez 16 09:47:26 machine ModemManager[1153]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.2/00
Dez 16 09:47:26 machine kernel: igb 0000:21:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0141] device (eno1): carrier: link connected
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0143] device (eno1): state change: unavailable -> disconnected (reason 'c
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0154] policy: auto-activating connection 'Hausnetz NAS-DNS' (5c70ea29-733
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0157] device (eno1): Activation: starting connection 'Hausnetz NAS-DNS' (
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0158] device (eno1): state change: disconnected -> prepare (reason 'none'
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0162] manager: NetworkManager state is now CONNECTING
Dez 16 09:47:27 machine kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0618] device (eno1): state change: prepare -> config (reason 'none', sys-
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0640] device (eno1): state change: config -> ip-config (reason 'none', sy
Dez 16 09:47:27 machine avahi-daemon[1196]: Joining mDNS multicast group on interface eno1.IPv6 with address fe80::403c:88bc:d6d0:a90e.
Dez 16 09:47:27 machine avahi-daemon[1196]: New relevant interface eno1.IPv6 for mDNS.
Dez 16 09:47:27 machine avahi-daemon[1196]: Registering new address record for fe80::403c:88bc:d6d0:a90e on eno1.*.
Dez 16 09:47:27 machine avahi-daemon[1196]: Joining mDNS multicast group on interface eno1.IPv4 with address 192.168.233.54.
Dez 16 09:47:27 machine avahi-daemon[1196]: New relevant interface eno1.IPv4 for mDNS.
Dez 16 09:47:27 machine avahi-daemon[1196]: Registering new address record for 192.168.233.54 on eno1.IPv4.
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0662] device (eno1): state change: ip-config -> ip-check (reason 'none', 
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0679] device (eno1): state change: ip-check -> secondaries (reason 'none'
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0681] device (eno1): state change: secondaries -> activated (reason 'none
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0684] manager: NetworkManager state is now CONNECTED_LOCAL
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0694] manager: NetworkManager state is now CONNECTED_SITE
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0695] policy: set 'Hausnetz NAS-DNS' (eno1) as default for IPv4 routing a
Dez 16 09:47:27 machine NetworkManager[1189]: <info>  [1608108447.0770] device (eno1): Activation: successful, device activated.
Dez 16 09:47:29 machine kernel: igb 0000:21:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Dez 16 09:47:30 machine NetworkManager[1189]: <info>  [1608108450.2219] device (eno1): carrier: link connected
Dez 16 09:47:32 machine avahi-daemon[1196]: Leaving mDNS multicast group on interface eno1.IPv6 with address fe80::403c:88bc:d6d0:a90e.
Dez 16 09:47:32 machine avahi-daemon[1196]: Joining mDNS multicast group on interface eno1.IPv6 with address 2001:4dd7:56f:0:d1a5:2262:955c
Dez 16 09:47:32 machine avahi-daemon[1196]: Registering new address record for 2001:4dd7:56f:0:d1a5:2262:955c:2fc4 on eno1.*.
Dez 16 09:47:32 machine avahi-daemon[1196]: Withdrawing address record for fe80::403c:88bc:d6d0:a90e on eno1.
Dez 16 09:47:32 machine NetworkManager[1189]: <info>  [1608108452.0602] policy: set 'Hausnetz NAS-DNS' (eno1) as default for IPv6 routing a
Dez 16 09:47:33 machine kernel: usb 3-2.4.4: usbfs: process 2677 (nitrokey-app) did not claim interface 0 before use
Dez 16 09:47:33 machine NetworkManager[1189]: <info>  [1608108453.1749] manager: NetworkManager state is now CONNECTED_GLOBAL
Dez 16 09:47:33 machine avahi-daemon[1196]: Registering new address record for 2001:4dd7:56f:0:1d48:580b:f481:c0fe on eno1.*.
Dez 16 09:47:45 machine kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1909188, emitted seq=1909190
Dez 16 09:47:45 machine kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1335 thread Xorg:cs0 pid 1
Dez 16 09:47:45 machine kernel: amdgpu 0000:27:00.0: amdgpu: GPU reset begin!
Dez 16 09:47:45 machine kernel: amdgpu: cp is busy, skip halt cp
Dez 16 09:47:45 machine kernel: amdgpu: rlc is busy, skip halt rlc
Dez 16 09:47:45 machine kernel: amdgpu 0000:27:00.0: amdgpu: GPU BACO reset
Dez 16 09:47:46 machine kernel: amdgpu 0000:27:00.0: amdgpu: GPU reset succeeded, trying to resume
Dez 16 09:47:46 machine kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
Dez 16 09:47:46 machine kernel: [drm] VRAM is lost due to GPU reset!
Dez 16 09:47:46 machine kernel: [drm] UVD and UVD ENC initialized successfully.
Dez 16 09:47:46 machine kernel: [drm] VCE initialized successfully.
Dez 16 09:47:46 machine kernel: [drm] recover vram bo from shadow start
Dez 16 09:47:46 machine kernel: [drm] recover vram bo from shadow done
Dez 16 09:47:46 machine kernel: [drm] Skip scheduling IBs!
Dez 16 09:47:46 machine kernel: [drm] Skip scheduling IBs!
Dez 16 09:47:46 machine kernel: amdgpu 0000:27:00.0: amdgpu: GPU reset(2) succeeded!
Dez 16 09:47:46 machine kernel: [drm] Skip scheduling IBs!
Dez 16 09:47:46 machine kernel: [drm] Skip scheduling IBs!
Dez 16 09:47:46 machine kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Dez 16 09:47:55 machine kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

I have plenty of logs showing more or less the same errors.

Anybody with a solution?

 

0 Likes
1 Reply
rhyzom
Journeyman III

Scrambled screen, disconnected keyboard, xen 4.14, debian 10, AMD RX 550

Looks like there is no problem if I boot debian 10 with the same kernel (5.9.0.4) but without xen 4.14 (but I switched to 4.14 because I had the same issues with 4.11).

0 Likes