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: Thu, 22 Nov 2018 18:47:58 +0000 [thread overview]
Message-ID: <bug-105733-502-7AmeAuU9eW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105733-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 5340 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105733
--- Comment #51 from Allan <allan4229@gmail.com> ---
Tried to install the RX480 on the other PC : the card is too big that it
touches the RAM slot's tabs. Can't install it.
In time, seems like the errors delay a little bit when setting
randomize_va_space=0. Was testing it for the CPU and noticed that amdgpu
delayed to fail, but it still failed.
What happened :
- the screen got granulated with pinkish colors as usual
- desktop extended this behavior
- but I could operate the system
- tty was black and white (normal)
- I could restart x server
- colors got normal after restarting
- tried the same application again
- crashed and froze the system
Main difference :
- now sometimes I can kill the tasks/restart xserver
I registered the times of each event, here follows:
(Firefox was opened in background while I tried to play Left for Dead 2 through
steam)
1. Recoverable delay with granulated colors (l4d2 begins 11:48, occurs 11:50
after some delay while loading the game menu)
> [Thu Nov 22 11:48:03 2018] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=11477, emitted seq=11480
> [Thu Nov 22 11:48:03 2018] amdgpu 0000:09:00.0: GPU reset begin!
> [Thu Nov 22 11:48:03 2018] amdgpu 0000:09:00.0: GPU pci config reset
> [Thu Nov 22 11:48:03 2018] amdgpu 0000:09:00.0: GPU reset succeeded, trying to resume
> [Thu Nov 22 11:48:03 2018] [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
> [Thu Nov 22 11:48:03 2018] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is lost!
> [Thu Nov 22 11:48:04 2018] amdgpu 0000:09:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring comp_1.3.1 test failed (-110)
> [Thu Nov 22 11:48:04 2018] [drm] UVD and UVD ENC initialized successfully.
> [Thu Nov 22 11:48:04 2018] [drm] VCE initialized successfully.
> [Thu Nov 22 11:48:04 2018] [drm] recover vram bo from shadow start
> [Thu Nov 22 11:48:04 2018] [drm] recover vram bo from shadow done
> [Thu Nov 22 11:48:04 2018] [drm] Skip scheduling IBs!
> [Thu Nov 22 11:48:04 2018] [drm] Skip scheduling IBs!
> [Thu Nov 22 11:48:04 2018] amdgpu 0000:09:00.0: GPU reset(1) succeeded!
> [Thu Nov 22 11:48:04 2018] [drm] Skip scheduling IBs!
> [Thu Nov 22 11:48:04 2018] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
> [Thu Nov 22 11:48:04 2018] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
> [Thu Nov 22 11:48:04 2018] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
> [Thu Nov 22 11:48:04 2018] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
> [Thu Nov 22 11:48:06 2018] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
> [Thu Nov 22 11:50:46 2018] show_signal_msg: 9 callbacks suppressed
> [Thu Nov 22 11:50:46 2018] Chrome_~dThread[1734]: segfault at 0 ip 00007f7926c4c181 sp 00007f792493aad0 error 6 in libxul.so[7f7926c38000+3a2c000]
> [Thu Nov 22 11:50:46 2018] Code: 15 dc f2 5f 04 48 89 10 c7 04 25 00 00 00 00 7c 09 00 00 e8 21 60 ff ff 90 48 8b 05 f9 2a 9b 05 48 8d 0d 22 f3 5f 04 48 89 08 <c7> 04 25 00 00 00 00 02 0a 00 00 e8 ff 5f ff ff e8 0a f3 ff ff 48
> [Thu Nov 22 11:50:46 2018] Chrome_~dThread[1885]: segfault at 0 ip 00007f7fa150a181 sp 00007f7f9f1f8ad0 error 6 in libxul.so[7f7fa14f6000+3a2c000]
> [Thu Nov 22 11:50:46 2018] Chrome_~dThread[8072]: segfault at 0 ip 00007fffededa181 sp 00007fffebbc8ad0 error 6
> [Thu Nov 22 11:50:46 2018] Code: 15 dc f2 5f 04 48 89 10 c7 04 25 00 00 00 00 7c 09 00 00 e8 21 60 ff ff 90 48 8b 05 f9 2a 9b 05 48 8d 0d 22 f3 5f 04 48 89 08 <c7> 04 25 00 00 00 00 02 0a 00 00 e8 ff 5f ff ff e8 0a f3 ff ff 48
> [Thu Nov 22 11:50:46 2018] in libxul.so[7fffedec6000+3a2c000]
> [Thu Nov 22 11:50:46 2018] Code: 15 dc f2 5f 04 48 89 10 c7 04 25 00 00 00 00 7c 09 00 00 e8 21 60 ff ff 90 48 8b 05 f9 2a 9b 05 48 8d 0d 22 f3 5f 04 48 89 08 <c7> 04 25 00 00 00 00 02 0a 00 00 e8 ff 5f ff ff e8 0a f3 ff ff 48
> [Thu Nov 22 11:50:46 2018] Chrome_~dThread[1931]: segfault at 0 ip 00007f8dc581f181 sp 00007f8dc350dad0 error 6 in libxul.so[7f8dc580b000+3a2c000]
> [Thu Nov 22 11:50:46 2018] Code: 15 dc f2 5f 04 48 89 10 c7 04 25 00 00 00 00 7c 09 00 00 e8 21 60 ff ff 90 48 8b 05 f9 2a 9b 05 48 8d 0d 22 f3 5f 04 48 89 08 <c7> 04 25 00 00 00 00 02 0a 00 00 e8 ff 5f ff ff e8 0a f3 ff ff 48
kern.log = dmesg
2. Unrecoverable crash (l4d2 begins 12:00, goes well until 12:55 when crashes
everything)
dmesg:
> [Thu Nov 22 12:55:04 2018] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1688198, emitted seq=1688200
> [Thu Nov 22 12:55:04 2018] amdgpu 0000:09:00.0: GPU reset begin!
> [Thu Nov 22 12:55:14 2018] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:46:crtc-0] hw_done or flip_done timed out
kern.log = dmesg
Xorg log is not reporting anything useful.
(In reply to russianneuromancer from comment #50)
> Can't tell you about RX480, but I know for sure that at least Vega 64 is
> totally fine with 1800X PCI-controller, no single not-solvable
> graphics-related issue for a year (so far all issues I had was solved by
> upgrading kernel and/or Mesa).
I wish I had this luck.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6503 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
next prev parent reply other threads:[~2018-11-22 18:47 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
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 [this message]
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-7AmeAuU9eW@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).