dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105733] Amdgpu randomly hangs and only ssh works. Mouse cursor moves sometimes but does nothing. Keyboard stops working.
Date: Wed, 02 May 2018 07:51:57 +0000	[thread overview]
Message-ID: <bug-105733-502-QqawEJOBW8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105733-502@http.bugs.freedesktop.org/>


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

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

--- Comment #13 from emmanuel.boudreault@polymtl.ca ---
I seem to have this same issue when opening an e-mail with a certain picture
using emacs. I'm using ArchLinux and Wayland (gnome shell). It is very easy to
reproduce so let me know if more logs/debugging can help.

AMD Ryzen 5 1600
Radeon RX 560
Kernel: 4.16.5-1-ARCH
amdgpu 18.0.1-1
mesa 18.0.1-1


These are the drm and amd related dmseg logs:

[    3.516074] amdgpu 0000:20:00.0: Invalid PCI ROM header signature: expecting
0xaa55, got 0xffff
[    3.516140] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment
size is 9-bit
[    3.516703] amdgpu 0000:20:00.0: VRAM: 4096M 0x000000F400000000 -
0x000000F4FFFFFFFF (4096M used)
[    3.516707] amdgpu 0000:20:00.0: GTT: 256M 0x0000000000000000 -
0x000000000FFFFFFF
[    3.516716] [drm] Detected VRAM RAM=4096M, BAR=256M
[    3.516718] [drm] RAM width 128bits GDDR5
[    3.516870] [drm] amdgpu: 4096M of VRAM memory ready
[    3.516873] [drm] amdgpu: 4096M of GTT memory ready.
[    3.516891] [drm] GART: num cpu pages 65536, num gpu pages 65536
[    3.517011] [drm] PCIE GART of 256M enabled (table at 0x000000F400040000).
[    3.517987] [drm] Chained IB support enabled!
[    3.524025] [drm] Found UVD firmware Version: 1.130 Family ID: 16
[    3.525784] [drm] Found VCE firmware Version: 52.4 Binary ID: 3
[    3.597334] amdgpu: [powerplay] 
[    3.597356] amdgpu: [powerplay] 
[    3.606949] [drm] DM_PPLIB: values for Engine clock
[    3.606951] [drm] DM_PPLIB:   21400
[    3.606952] [drm] DM_PPLIB:   38700
[    3.606953] [drm] DM_PPLIB:   84300
[    3.606953] [drm] DM_PPLIB:   99500
[    3.606954] [drm] DM_PPLIB:   106200
[    3.606955] [drm] DM_PPLIB:   110800
[    3.606956] [drm] DM_PPLIB:   114900
[    3.606956] [drm] DM_PPLIB:   122600
[    3.606957] [drm] DM_PPLIB: Validation clocks:
[    3.606958] [drm] DM_PPLIB:    engine_max_clock: 122600
[    3.606959] [drm] DM_PPLIB:    memory_max_clock: 150000
[    3.606960] [drm] DM_PPLIB:    level           : 0
[    3.606962] [drm] DM_PPLIB: values for Memory clock
[    3.606963] [drm] DM_PPLIB:   30000
[    3.606964] [drm] DM_PPLIB:   62500
[    3.606964] [drm] DM_PPLIB:   150000
[    3.606965] [drm] DM_PPLIB: Validation clocks:
[    3.606966] [drm] DM_PPLIB:    engine_max_clock: 122600
[    3.606967] [drm] DM_PPLIB:    memory_max_clock: 150000
[    3.606967] [drm] DM_PPLIB:    level           : 0
[    3.617049] [drm] Display Core initialized with v3.1.27!
[    3.642678] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.642680] [drm] Driver supports precise vblank timestamp query.
[    3.672521] [drm] UVD and UVD ENC initialized successfully.
[    3.773428] [drm] VCE initialized successfully.
[    4.301585] [drm] fb mappable at 0xE056A000
[    4.301587] [drm] vram apper at 0xE0000000
[    4.301588] [drm] size 11059200
[    4.301589] [drm] fb depth is 24
[    4.301590] [drm]    pitch is 10240
[    4.301702] fbcon: amdgpudrmfb (fb0) is primary device
[    4.358740] amdgpu 0000:20:00.0: fb0: amdgpudrmfb frame buffer device
[    4.371876] [drm] Initialized amdgpu 3.23.0 20150101 for 0000:20:00.0 on
minor 0
[   55.222527] amdgpu 0000:20:00.0: GPU fault detected: 147 0x04f04802
[   55.222536] amdgpu 0000:20:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x0050309E
[   55.222540] amdgpu 0000:20:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x06048002
[   55.222545] amdgpu 0000:20:00.0: VM fault (0x02, vmid 3) at page 5255326,
read from 'TC0' (0x54433000) (72)
[   65.330363] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
last signaled seq=701, last emitted seq=704
[   65.330378] [drm] IP block:gfx_v8_0 is hung!
[   65.330425] [drm] GPU recovery disabled.

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

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

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

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

  parent reply	other threads:[~2018-05-02  7:51 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-25  4:47 [Bug 105733] Amdgpu randomly hangs and only ssh works. Mouse cursor moves sometimes but does nothing. Keyboard stops working bugzilla-daemon
2018-03-25  4:49 ` bugzilla-daemon
2018-03-25 16:52 ` bugzilla-daemon
2018-03-27  3:02 ` bugzilla-daemon
2018-03-27 11:52 ` bugzilla-daemon
2018-03-28 15:34 ` bugzilla-daemon
2018-04-01 14:15 ` bugzilla-daemon
2018-04-04 20:49 ` bugzilla-daemon
2018-04-09  1:19 ` bugzilla-daemon
2018-04-09  1:22 ` bugzilla-daemon
2018-04-11  9:31 ` bugzilla-daemon
2018-04-27 11:26 ` bugzilla-daemon
2018-04-27 12:41 ` bugzilla-daemon
2018-05-02  7:51 ` bugzilla-daemon [this message]
2018-05-08  7:38 ` bugzilla-daemon
2018-07-08 12:11 ` bugzilla-daemon
2018-07-26  8:20 ` bugzilla-daemon
2018-07-26  8:26 ` bugzilla-daemon
2018-07-26  8:27 ` bugzilla-daemon
2018-07-26  8:31 ` bugzilla-daemon
2018-07-26  8:32 ` bugzilla-daemon
2018-07-26  9:09 ` bugzilla-daemon
2018-07-26  9:19 ` bugzilla-daemon
2018-08-13  2:24 ` bugzilla-daemon
2018-08-13  2:25 ` bugzilla-daemon
2018-08-14 19:46 ` bugzilla-daemon
2018-08-14 20:32 ` bugzilla-daemon
2018-08-15  7:11 ` bugzilla-daemon
2018-08-23 19:10 ` bugzilla-daemon
2018-08-23 19:33 ` bugzilla-daemon
2018-08-24 12:35 ` bugzilla-daemon
2018-08-26 11:18 ` bugzilla-daemon
2018-08-26 22:02 ` bugzilla-daemon
2018-08-27 21:55 ` bugzilla-daemon
2018-08-30 20:01 ` bugzilla-daemon
2018-08-31  9:04 ` bugzilla-daemon
2018-09-03  8:46 ` bugzilla-daemon
2018-09-06 13:06 ` bugzilla-daemon
2018-09-14 16:33 ` bugzilla-daemon
2018-10-31 12:49 ` bugzilla-daemon
2018-11-04  1:19 ` bugzilla-daemon
2018-11-16 14:28 ` bugzilla-daemon
2018-11-16 14:44 ` bugzilla-daemon
2018-11-17 13:28 ` bugzilla-daemon
2018-11-17 15:36 ` bugzilla-daemon
2018-11-19  5:08 ` bugzilla-daemon
2018-11-19  5:31 ` bugzilla-daemon
2018-11-20 14:15 ` bugzilla-daemon
2019-02-05 16:27   ` Garry Hurley
2018-11-20 15:18 ` bugzilla-daemon
2018-11-20 20:32 ` bugzilla-daemon
2018-11-21  0:52 ` bugzilla-daemon
2018-11-22 18:47 ` bugzilla-daemon
2018-11-22 19:27 ` bugzilla-daemon
2018-11-22 19:28 ` bugzilla-daemon
2019-01-15 14:18 ` bugzilla-daemon
2019-01-17 22:25 ` bugzilla-daemon
2019-01-17 22:32 ` bugzilla-daemon
2019-01-23 19:44 ` bugzilla-daemon
2019-01-23 19:46 ` bugzilla-daemon
2019-01-23 20:23 ` bugzilla-daemon
2019-01-23 21:05 ` bugzilla-daemon
2019-01-25  7:36 ` bugzilla-daemon
2019-01-25  8:20 ` bugzilla-daemon
2019-01-26 13:18 ` bugzilla-daemon
2019-02-02 10:55 ` bugzilla-daemon
2019-02-04  3:17 ` bugzilla-daemon
2019-02-04 18:38 ` bugzilla-daemon
2019-02-04 18:42 ` bugzilla-daemon
2019-02-05  2:18 ` bugzilla-daemon
2019-02-05 13:42 ` bugzilla-daemon
2019-02-05 16:28 ` bugzilla-daemon
2019-02-10  0:13 ` bugzilla-daemon
2019-02-23 12:14 ` bugzilla-daemon
2019-03-09 10:31 ` bugzilla-daemon
2019-03-10  9:37 ` bugzilla-daemon
2019-03-10 10:03 ` bugzilla-daemon
2019-03-10 10:07 ` bugzilla-daemon
2019-03-10 10:55 ` bugzilla-daemon
2019-03-11  6:49 ` bugzilla-daemon
2019-03-12  8:35 ` bugzilla-daemon
2019-07-16 10:18 ` bugzilla-daemon
2019-07-17  3:00 ` bugzilla-daemon
2019-07-17  7:58 ` 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-105733-502-QqawEJOBW8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).