Attachment 129338 Details for Bug 99680 – VM and GPU faults

VM and GPU faults

vm_fault.txt (text/plain), 7.47 KB, created by SET on 2017-02-04 19:20:40 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: SET

Created: 2017-02-04 19:20:40 UTC

Size: 7.47 KB

patch

obsolete

>$ dmesg |grep -i amdgpu         
>[   14.091002] [drm] amdgpu kernel modesetting enabled.
>[   14.516585] fb: switching to amdgpudrmfb from EFI VGA
>[   14.517474] amdgpu 0000:00:01.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
>[   14.517476] amdgpu 0000:00:01.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
>[   14.517598] [drm] amdgpu: 1024M of VRAM memory ready
>[   14.517599] [drm] amdgpu: 1024M of GTT memory ready.
>[   14.620310] amdgpu 0000:00:01.0: amdgpu: using MSI.
>[   14.620338] [drm] amdgpu: irq initialized.
>[   14.620366] [drm] amdgpu: dpm initialized
>[   14.620894] [drm] amdgpu atom DIG backlight initialized
>[   14.620896] [drm] AMDGPU Display Connectors
>[   15.203212] amdgpu 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000010, cpu addr 0xffff88034b9f5010
>[   15.203509] amdgpu 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000020, cpu addr 0xffff88034b9f5020
>[   15.203627] amdgpu 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000030, cpu addr 0xffff88034b9f5030
>[   15.203765] amdgpu 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000040, cpu addr 0xffff88034b9f5040
>[   15.203887] amdgpu 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000050, cpu addr 0xffff88034b9f5050
>[   15.204003] amdgpu 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000040000060, cpu addr 0xffff88034b9f5060
>[   15.204127] amdgpu 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000040000070, cpu addr 0xffff88034b9f5070
>[   15.204220] amdgpu 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000040000080, cpu addr 0xffff88034b9f5080
>[   15.204297] amdgpu 0000:00:01.0: fence driver on ring 8 use gpu addr 0x0000000040000090, cpu addr 0xffff88034b9f5090
>[   15.255983] amdgpu 0000:00:01.0: fence driver on ring 9 use gpu addr 0x00000000400000a0, cpu addr 0xffff88034b9f50a0
>[   15.256237] amdgpu 0000:00:01.0: fence driver on ring 10 use gpu addr 0x00000000400000b0, cpu addr 0xffff88034b9f50b0
>[   15.299521] amdgpu 0000:00:01.0: fence driver on ring 11 use gpu addr 0x000000000028cd30, cpu addr 0xffffc90003838d30
>[   15.358223] amdgpu 0000:00:01.0: fence driver on ring 12 use gpu addr 0x00000000400000d0, cpu addr 0xffff88034b9f50d0
>[   15.358456] amdgpu 0000:00:01.0: fence driver on ring 13 use gpu addr 0x00000000400000e0, cpu addr 0xffff88034b9f50e0
>[   16.512656] fbcon: amdgpudrmfb (fb0) is primary device
>[   20.630738] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device
>[   20.830505] [drm] Initialized amdgpu 3.9.0 20150101 for 0000:00:01.0 on minor 0
>[   20.830633] amdgpu 0000:01:00.0: enabling device (0000 -> 0003)
>[   20.984813] amdgpu 0000:01:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
>[   20.984820] amdgpu 0000:01:00.0: GTT: 2048M 0x0000000080000000 - 0x00000000FFFFFFFF
>[   20.984892] [drm] amdgpu: 2048M of VRAM memory ready
>[   20.984894] [drm] amdgpu: 2048M of GTT memory ready.
>[   20.985954] amdgpu 0000:01:00.0: amdgpu: using MSI.
>[   20.986004] [drm] amdgpu: irq initialized.                                                                                    
>[   20.986128] amdgpu: powerplay initialized                                                                                     
>[   21.003572] amdgpu 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000010, cpu addr 0xffff880343e2e010          
>[   21.003752] amdgpu 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000020, cpu addr 0xffff880343e2e020
>[   21.003861] amdgpu 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000030, cpu addr 0xffff880343e2e030
>[   21.003995] amdgpu 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000040, cpu addr 0xffff880343e2e040
>[   21.004107] amdgpu 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000050, cpu addr 0xffff880343e2e050
>[   21.004205] amdgpu 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000080000060, cpu addr 0xffff880343e2e060
>[   21.004287] amdgpu 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000080000070, cpu addr 0xffff880343e2e070
>[   21.004360] amdgpu 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000080000080, cpu addr 0xffff880343e2e080
>[   21.004448] amdgpu 0000:01:00.0: fence driver on ring 8 use gpu addr 0x0000000080000090, cpu addr 0xffff880343e2e090
>[   21.017729] amdgpu 0000:01:00.0: fence driver on ring 9 use gpu addr 0x00000000800000a0, cpu addr 0xffff880343e2e0a0
>[   21.017948] amdgpu 0000:01:00.0: fence driver on ring 10 use gpu addr 0x00000000800000b0, cpu addr 0xffff880343e2e0b0
>[   21.034054] [drm] Initialized amdgpu 3.9.0 20150101 for 0000:01:00.0 on minor 1
>[   56.189848] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
>[   56.189939] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
>[   56.899066] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
>[   56.899106] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
>[  132.020564] amdgpu 0000:00:01.0: GPU fault detected: 146 0x03450014
>[  132.020575] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0010869A
>[  132.020581] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x05000014
>[  132.020588] amdgpu 0000:00:01.0: VM fault (0x14, vmid 2) at page 1083034, write from 'CB0' (0x43423000) (0)
>[  161.163619] amdgpu 0000:00:01.0: GPU fault detected: 146 0x0ea4040c
>[  161.163631] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00101075
>[  161.163637] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0400400C
>[  161.163645] amdgpu 0000:00:01.0: VM fault (0x0c, vmid 2) at page 1052789, read from 'DB0' (0x44423000) (4)
>[  161.163655] amdgpu 0000:00:01.0: GPU fault detected: 146 0x0e24040c
>[  161.163661] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00101072
>[  161.163667] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0400400C
>[  161.163674] amdgpu 0000:00:01.0: VM fault (0x0c, vmid 2) at page 1052786, read from 'DB0' (0x44423000) (4)
>[  161.165259] amdgpu 0000:00:01.0: GPU fault detected: 146 0x0ecc040c
>[  161.165267] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00101076
>[  161.165271] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C00400C
>[  161.165278] amdgpu 0000:00:01.0: VM fault (0x0c, vmid 6) at page 1052790, read from 'DB0' (0x44423000) (4)
>[  161.167926] amdgpu 0000:00:01.0: GPU fault detected: 146 0x0ec4040c
>[  161.167935] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00101076
>[  161.167940] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0400400C
>[  161.167947] amdgpu 0000:00:01.0: VM fault (0x0c, vmid 2) at page 1052790, read from 'DB0' (0x44423000) (4)
>[ 3244.139771] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
>[ 3244.139811] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
>[ 3244.783457] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
>[ 3244.783498] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
>
>$ dmesg |head
>[    0.000000] Linux version 4.10.0-rc6-git-00167-ga0a2864-dirty (user@localhost.localdomain) (gcc version 6.2.1 20160830 (GCC) ) #9 SMP PREEMPT Sat Feb 4 13:10:12 CET 2017
>[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux-git root=UUID=76ba28b4-683c-4a39-96ef-6a1105905567 rw quiet
>
># cat /etc/modprobe.d/amdgpu.conf 
>install radeon /bin/false
>options amdgpu aspm=0 bapm=0 runpm=0 powerplay=1 dpm=1 pg_mask=1 cg_mask=1

Actions: View

Attachments on bug 99680: 129338

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.