What do these Dom0 messages mean?

[Ulrich Windl]

Hi!

I'm watching Dom0 journal messages, and I'm wondering about some of
those (marked with ### blocks):

...during initializing the AMD graphics card...
Feb 12 22:25:14 dom0 kernel: [drm] VCE enabled in VM mode
###
Feb 12 22:25:14 dom0 kernel: resource sanity check: requesting [mem
0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem
0x000dc000-0x000dffff window]
Feb 12 22:25:14 dom0 kernel: caller pci_map_rom+0x6a/0x1d0 mapping
multiple BARs
###
Feb 12 22:25:14 dom0 kernel: amdgpu 0000:01:00.0: No more image in the
PCI ROM
Feb 12 22:25:14 dom0 kernel: ATOM BIOS: 113-TIC33062-001
Feb 12 22:25:14 dom0 kernel: [drm] vm size is 64 GB, 2 levels, block
size is 10-bit, fragment size is 9-bit
Feb 12 22:25:14 dom0 kernel: amdgpu 0000:01:00.0: VRAM: 4096M
0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
Feb 12 22:25:14 dom0 kernel: amdgpu 0000:01:00.0: GART: 256M
0x0000000000000000 - 0x000000000FFFFFFF
Feb 12 22:25:14 dom0 kernel: [drm] Detected VRAM RAM=4096M, BAR=256M
Feb 12 22:25:14 dom0 kernel: [drm] RAM width 128bits GDDR5
Feb 12 22:25:14 dom0 kernel: [TTM] Zone kernel: Available graphics
memory: 2009316 kiB
...
Feb 12 22:25:15 dom0 kernel: amdgpu: [powerplay] Failed to retrieve
minimum clocks.
...

...initializing firewire...
Feb 12 22:25:14 dom0 kernel: firewire_ohci 0000:05:02.0: added OHCI
v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x41
Feb 12 22:25:14 dom0 kernel: firewire_ohci 0000:05:02.0: DMA context
ARReq has stopped, error code: evt_unknown
Feb 12 22:25:14 dom0 kernel: firewire_ohci 0000:05:02.0: DMA context
ARReq has stopped, error code: evt_unknown
Feb 12 22:25:14 dom0 kernel: firewire_ohci 0000:05:02.0: DMA context
ARRsp has stopped, error code: evt_unknown
Feb 12 22:25:14 dom0 kernel: firewire_ohci 0000:05:02.0: bad self ID 0/1
(00000000 != ~00000000)
...

...
Apr 13 19:38:34 dom0 kernel: pciback 0000:03:00.0: Driver tried to write
to a read-only configuration space field at offset 0xb2, size 2. This
may be harmless, but i
1) see permissive attribute in sysfs
2) report problems to the xen-devel
mailing list along with details of your device obtained from lspci.
...

Why are those messages repeating so fast?
...
Apr 13 19:48:07 dom0 qrexec[9736]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
Apr 13 19:48:08 dom0 qrexec[9738]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
Apr 13 19:48:09 dom0 qrexec[9740]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
Apr 13 19:48:10 dom0 qrexec[9742]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
Apr 13 19:48:10 dom0 qrexec[9743]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
Apr 13 19:48:10 dom0 qrexec[9744]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
Apr 13 19:48:10 dom0 qrexec[9748]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
Apr 13 19:48:11 dom0 qrexec[9751]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
Apr 13 19:48:11 dom0 qrexec[9750]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
Apr 13 19:48:11 dom0 qrexec[9754]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
Apr 13 19:48:11 dom0 qrexec[9756]: qubes.UpdatesProxy: fedora-30 -> :
allowed to sys-net
...

...
Apr 13 20:10:31 dom0 qrexec[16588]: whonix.SdwdateStatus: sys-whonix ->
whonix-ws-15-dvm: allowed to whonix-ws-15-dvm
Apr 13 20:10:32 dom0 run-parts[16593]: (/etc/cron.daily) finished
qubes-dom0-updates.cron
Apr 13 20:10:32 dom0 anacron[15604]: Job `cron.daily' terminated
(mailing output)
Apr 13 20:10:32 dom0 anacron[15604]: Can't find sendmail at
/usr/sbin/sendmail, not mailing output
...

What is that about?

...
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S3 disabled
Apr 13 20:34:35 dom0 libvirtd[4941]: S4 disabled
Apr 13 20:34:35 dom0 systemd[1]: Stopped Virtualization daemon.
...

Regards,
Ulrich