All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110674] Crashes / Resets From AMDGPU / Radeon VII
Date: Sat, 15 Jun 2019 16:58:59 +0000	[thread overview]
Message-ID: <bug-110674-502-eQSQgugfon@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110674-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2922 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=110674

--- Comment #37 from Tom B <tom@r.je> ---
5.1.9 makes this bug even worse. It now crashes as soon as the display server
is started.

Running sensors now gives an error:


ERROR: Can't get value of subfeature fan1_input: I/O error
ERROR: Can't get value of subfeature power1_average: I/O error
iwlwifi-virtual-0
Adapter: Virtual device
temp1:        +37.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +34.8°C  (high = +70.0°C)
Tctl:         +61.8°C  

amdgpu-pci-4400
Adapter: PCI adapter
vddgfx:       +0.74 V  
fan1:             N/A  (min =    0 RPM, max = 3850 RPM)
temp1:        +39.0°C  (crit = +118.0°C, hyst = -273.1°C)
power1:           N/A  (cap = 250.00 W)

k10temp-pci-00cb
Adapter: PCI adapter
Tdie:         +33.2°C  (high = +70.0°C)
Tctl:         +60.2°C  



I can't even see the wattage now. 

# cat /sys/kernel/debug/dri/0/amdgpu_pm_info

Clock Gating Flags Mask: 0x860200
        Graphics Medium Grain Clock Gating: Off
        Graphics Medium Grain memory Light Sleep: Off
        Graphics Coarse Grain Clock Gating: Off
        Graphics Coarse Grain memory Light Sleep: Off
        Graphics Coarse Grain Tree Shader Clock Gating: Off
        Graphics Coarse Grain Tree Shader Light Sleep: Off
        Graphics Command Processor Light Sleep: Off
        Graphics Run List Controller Light Sleep: Off
        Graphics 3D Coarse Grain Clock Gating: Off
        Graphics 3D Coarse Grain memory Light Sleep: Off
        Memory Controller Light Sleep: Off
        Memory Controller Medium Grain Clock Gating: On
        System Direct Memory Access Light Sleep: Off
        System Direct Memory Access Medium Grain Clock Gating: Off
        Bus Interface Medium Grain Clock Gating: Off
        Bus Interface Light Sleep: Off
        Unified Video Decoder Medium Grain Clock Gating: Off
        Video Compression Engine Medium Grain Clock Gating: Off
        Host Data Path Light Sleep: Off
        Host Data Path Medium Grain Clock Gating: Off
        Digital Right Management Medium Grain Clock Gating: Off
        Digital Right Management Light Sleep: On
        Rom Medium Grain Clock Gating: On
        Data Fabric Medium Grain Clock Gating: On

GFX Clocks and Power:
        1373 MHz (PSTATE_SCLK)
        1001 MHz (PSTATE_MCLK)
        737 mV (VDDGFX)

GPU Temperature: 39 C

UVD: Disabled

VCE: Disabled


No clocks or wattage! 

I'm guessing 34d07ce3d6a120056e4763ae9a3db0d769ab7c63 "fix ring test failure
issue during s3 in vce 3.0 (V2)" is to blame as dmesg (attached in next post)
says


[   20.584937] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=25, emitted seq=27

It would be nice to see some acknowledgement from AMD on this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3682 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-06-15 16:58 UTC|newest]

Thread overview: 179+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14  5:55 [Bug 110674] Crashes / Resets From AMDGPU / Radeon VII bugzilla-daemon
2019-05-14  5:55 ` bugzilla-daemon
2019-05-14  5:56 ` bugzilla-daemon
2019-05-14  5:56 ` bugzilla-daemon
2019-05-14  9:04 ` bugzilla-daemon
2019-05-14  9:05 ` bugzilla-daemon
2019-05-14  9:20 ` bugzilla-daemon
2019-05-14  9:34 ` bugzilla-daemon
2019-05-14 15:32 ` bugzilla-daemon
2019-05-15  2:15 ` bugzilla-daemon
2019-05-15  2:16 ` bugzilla-daemon
2019-05-15  3:05 ` bugzilla-daemon
2019-05-15  3:09 ` bugzilla-daemon
2019-05-15  3:09 ` bugzilla-daemon
2019-05-15  3:10 ` bugzilla-daemon
2019-05-15  3:10 ` bugzilla-daemon
2019-05-19  9:36 ` bugzilla-daemon
2019-05-19  9:39 ` bugzilla-daemon
2019-05-19 14:27 ` bugzilla-daemon
2019-05-19 17:52 ` bugzilla-daemon
2019-05-19 20:30 ` bugzilla-daemon
2019-05-19 20:53 ` bugzilla-daemon
2019-05-19 22:04 ` bugzilla-daemon
2019-05-19 22:05 ` bugzilla-daemon
2019-05-19 22:14 ` bugzilla-daemon
2019-05-19 22:19 ` bugzilla-daemon
2019-05-19 22:28 ` bugzilla-daemon
2019-05-19 22:37 ` bugzilla-daemon
2019-05-19 23:02 ` bugzilla-daemon
2019-05-19 23:05 ` bugzilla-daemon
2019-05-19 23:18 ` bugzilla-daemon
2019-05-19 23:49 ` bugzilla-daemon
2019-05-21  7:38 ` bugzilla-daemon
2019-05-21  8:11 ` bugzilla-daemon
2019-05-21  9:42 ` bugzilla-daemon
2019-05-30 16:15 ` bugzilla-daemon
2019-06-03 11:39 ` bugzilla-daemon
2019-06-03 14:57 ` bugzilla-daemon
2019-06-04  4:19 ` bugzilla-daemon
2019-06-04  4:21 ` bugzilla-daemon
2019-06-15 16:58 ` bugzilla-daemon [this message]
2019-06-15 16:59 ` bugzilla-daemon
2019-06-15 22:15 ` bugzilla-daemon
2019-06-16 16:05 ` bugzilla-daemon
2019-06-16 16:08 ` bugzilla-daemon
2019-06-17 10:18 ` bugzilla-daemon
2019-06-21 20:17 ` bugzilla-daemon
2019-06-21 20:18 ` bugzilla-daemon
2019-06-22  4:19 ` bugzilla-daemon
2019-06-22  4:20 ` bugzilla-daemon
2019-07-08 12:29 ` bugzilla-daemon
2019-07-25  5:36 ` bugzilla-daemon
2019-07-26  1:19 ` bugzilla-daemon
2019-07-26  1:24 ` bugzilla-daemon
2019-07-26  3:19 ` bugzilla-daemon
2019-07-28  5:20 ` bugzilla-daemon
2019-07-29 10:52 ` bugzilla-daemon
2019-07-29 19:25 ` bugzilla-daemon
2019-07-29 21:40 ` bugzilla-daemon
2019-07-31 15:37 ` bugzilla-daemon
2019-07-31 17:09 ` bugzilla-daemon
2019-07-31 17:13 ` bugzilla-daemon
2019-08-03 12:10 ` bugzilla-daemon
2019-08-03 12:31 ` bugzilla-daemon
2019-08-03 13:35 ` bugzilla-daemon
2019-08-08 14:37 ` bugzilla-daemon
2019-08-10 12:10 ` bugzilla-daemon
2019-08-10 13:02 ` bugzilla-daemon
2019-08-10 13:14 ` bugzilla-daemon
2019-08-10 13:15 ` bugzilla-daemon
2019-08-10 13:29 ` bugzilla-daemon
2019-08-10 16:39 ` bugzilla-daemon
2019-08-10 19:00 ` bugzilla-daemon
2019-08-11  1:15 ` bugzilla-daemon
2019-08-11 15:26 ` bugzilla-daemon
2019-08-11 17:00 ` bugzilla-daemon
2019-08-11 18:43 ` bugzilla-daemon
2019-08-11 18:45 ` bugzilla-daemon
2019-08-11 22:31 ` bugzilla-daemon
2019-08-11 23:44 ` bugzilla-daemon
2019-08-12  3:12 ` bugzilla-daemon
2019-08-12  3:29 ` bugzilla-daemon
2019-08-12  5:18 ` bugzilla-daemon
2019-08-12  5:58 ` bugzilla-daemon
2019-08-12 13:21 ` bugzilla-daemon
2019-08-12 14:34 ` bugzilla-daemon
2019-08-12 15:34 ` bugzilla-daemon
2019-08-12 15:42 ` bugzilla-daemon
2019-08-12 15:53 ` bugzilla-daemon
2019-08-12 15:56 ` bugzilla-daemon
2019-08-12 16:32 ` bugzilla-daemon
2019-08-12 16:38 ` bugzilla-daemon
2019-08-12 16:47 ` bugzilla-daemon
2019-08-12 16:57 ` bugzilla-daemon
2019-08-12 17:40 ` bugzilla-daemon
2019-08-12 18:37 ` bugzilla-daemon
2019-08-13  3:15 ` bugzilla-daemon
2019-08-13  3:33 ` bugzilla-daemon
2019-08-13 13:05 ` bugzilla-daemon
2019-08-13 13:35 ` bugzilla-daemon
2019-08-13 15:20 ` bugzilla-daemon
2019-08-13 17:11 ` bugzilla-daemon
2019-08-13 18:33 ` bugzilla-daemon
2019-08-14 15:44 ` bugzilla-daemon
2019-08-14 17:30 ` bugzilla-daemon
2019-08-16  5:58 ` bugzilla-daemon
2019-08-16 10:10 ` bugzilla-daemon
2019-08-16 10:35 ` bugzilla-daemon
2019-08-16 10:41 ` bugzilla-daemon
2019-08-16 13:10 ` bugzilla-daemon
2019-08-16 13:18 ` bugzilla-daemon
2019-08-16 14:17 ` bugzilla-daemon
2019-08-16 21:06 ` bugzilla-daemon
2019-08-16 22:14 ` bugzilla-daemon
2019-08-16 23:19 ` bugzilla-daemon
2019-08-17  1:47 ` bugzilla-daemon
2019-08-17  2:15 ` bugzilla-daemon
2019-08-17  2:37 ` bugzilla-daemon
2019-08-17  3:16 ` bugzilla-daemon
2019-08-17 13:37 ` bugzilla-daemon
2019-08-25 20:46 ` bugzilla-daemon
2019-08-25 20:47 ` bugzilla-daemon
2019-08-25 23:01 ` bugzilla-daemon
2019-08-26  3:20 ` bugzilla-daemon
2019-08-26  3:21 ` bugzilla-daemon
2019-08-26  3:47 ` bugzilla-daemon
2019-08-27 21:56 ` bugzilla-daemon
2019-08-31  0:11 ` bugzilla-daemon
2019-09-03 16:46 ` bugzilla-daemon
2019-09-18  9:52 ` bugzilla-daemon
2019-09-18 11:36 ` bugzilla-daemon
2019-09-20 19:12 ` bugzilla-daemon
2019-09-20 19:13 ` bugzilla-daemon
2019-09-21 15:02 ` bugzilla-daemon
2019-09-21 15:12 ` bugzilla-daemon
2019-09-21 15:25 ` bugzilla-daemon
2019-09-21 15:38 ` bugzilla-daemon
2019-09-21 15:57 ` bugzilla-daemon
2019-09-21 15:59 ` bugzilla-daemon
2019-09-21 19:54 ` bugzilla-daemon
2019-09-21 20:04 ` bugzilla-daemon
2019-09-22 21:36 ` bugzilla-daemon
2019-09-22 21:38 ` bugzilla-daemon
2019-09-23  4:09 ` bugzilla-daemon
2019-09-23  4:11 ` bugzilla-daemon
2019-09-23 14:19 ` bugzilla-daemon
2019-09-23 14:20 ` bugzilla-daemon
2019-09-23 15:40 ` bugzilla-daemon
2019-09-23 15:43 ` bugzilla-daemon
2019-09-23 16:04 ` bugzilla-daemon
2019-09-24  9:44 ` bugzilla-daemon
2019-09-27 14:46 ` bugzilla-daemon
2019-09-27 15:12 ` bugzilla-daemon
2019-09-27 15:13 ` bugzilla-daemon
2019-09-29 19:25 ` bugzilla-daemon
2019-09-29 19:28 ` bugzilla-daemon
2019-09-29 19:30 ` bugzilla-daemon
2019-09-30 20:20 ` bugzilla-daemon
2019-10-01 23:44 ` bugzilla-daemon
2019-10-03  6:54 ` bugzilla-daemon
2019-10-04 12:43 ` bugzilla-daemon
2019-10-06 14:16 ` bugzilla-daemon
2019-10-06 16:39 ` bugzilla-daemon
2019-10-06 17:06 ` bugzilla-daemon
2019-10-06 17:07 ` bugzilla-daemon
2019-10-10 12:50 ` bugzilla-daemon
2019-10-12 23:34 ` bugzilla-daemon
2019-10-14  9:15 ` bugzilla-daemon
2019-10-14 10:39 ` bugzilla-daemon
2019-10-14 11:37 ` bugzilla-daemon
2019-10-14 17:05 ` bugzilla-daemon
2019-10-19 17:35 ` bugzilla-daemon
2019-10-20 18:27 ` bugzilla-daemon
2019-10-21  8:11 ` bugzilla-daemon
2019-11-10 16:36 ` bugzilla-daemon
2019-11-10 17:45 ` bugzilla-daemon
2019-11-26 12:03 ` bugzilla-daemon
2019-11-26 14:14 ` bugzilla-daemon
2019-11-26 23:13 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-110674-502-eQSQgugfon@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.