Comment # 5
on bug 103949
from gernot.pokorny.dev@gmail.com
I got the same issue. My hardware is MSI X470 Gaming Plus AMD Ryzen 5 2600 XFX RX580 GTS Black Edition Log: gernot@pcname:~$ journalctl -b -p err -- Logs begin at Sun 2018-10-07 04:01:03 CEST, end at Mon 2019-01-28 15:51:03 CET. -- Jän 28 14:25:00 pcname kernel: Couldn't get size: 0x800000000000000e Jän 28 14:25:00 pcname kernel: MODSIGN: Couldn't get UEFI db list Jän 28 14:25:00 pcname kernel: Couldn't get size: 0x800000000000000e Jän 28 14:25:00 pcname kernel: Couldn't get size: 0x800000000000000e Jän 28 14:25:00 pcname kernel: amdgpu 0000:1d:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff Jän 28 14:25:00 pcname kernel: sd 10:0:0:0: [sdc] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 10:0:0:0: [sdc] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: sd 9:0:0:0: [sdd] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 9:0:0:0: [sdd] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: scsi 9:0:0:1: Wrong diagnostic page; asked for 1 got 8 Jän 28 14:25:00 pcname kernel: scsi 9:0:0:1: Failed to get diagnostic page 0x1 Jän 28 14:25:00 pcname kernel: scsi 9:0:0:1: Failed to bind enclosure -19 Jän 28 14:25:00 pcname kernel: sd 12:0:0:0: [sde] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 12:0:0:0: [sde] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: ses 14:0:0:1: Wrong diagnostic page; asked for 1 got 8 Jän 28 14:25:00 pcname kernel: ses 14:0:0:1: Failed to get diagnostic page 0x1 Jän 28 14:25:00 pcname kernel: ses 14:0:0:1: Failed to bind enclosure -19 Jän 28 14:25:00 pcname kernel: sd 14:0:0:0: [sdg] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 14:0:0:0: [sdg] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: ses 16:0:0:1: Wrong diagnostic page; asked for 1 got 8 Jän 28 14:25:00 pcname kernel: ses 16:0:0:1: Failed to get diagnostic page 0x1 Jän 28 14:25:00 pcname kernel: ses 16:0:0:1: Failed to bind enclosure -19 Jän 28 14:25:00 pcname kernel: sd 16:0:0:0: [sdj] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 16:0:0:0: [sdj] Assuming drive cache: write through Jän 28 14:25:05 pcname spice-vdagent[1727]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Jän 28 14:25:10 pcname colord-sane[1833]: io/hpmud/pp.c 627: unable to read device-id ret=-1 Jän 28 14:27:09 pcname spice-vdagent[2694]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Jän 28 14:27:09 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:09 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:33 pcname pulseaudio[2597]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote app Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
