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: Sun, 25 Mar 2018 04:47:54 +0000 [thread overview]
Message-ID: <bug-105733-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3250 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105733
Bug ID: 105733
Summary: Amdgpu randomly hangs and only ssh works. Mouse cursor
moves sometimes but does nothing. Keyboard stops
working.
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: allan4229@gmail.com
Created attachment 138344
--> https://bugs.freedesktop.org/attachment.cgi?id=138344&action=edit
dmesg, killing pids, shutting down, unloading amdgpu, xorg log
WHAT HAPPENS
- Amdgpu hangs without any clear clue of what is happening.
- The mouse cursor responds to movements when the system is not frozen, but
also it does nothing as well.
- The keyboard gets num lock frozen and even trying with a ps2 one does not
work.
- The video gets frozen.
- Only ssh works, but only the times that the system is not frozen, of course.
- The most irritating part : the system can not be shutdown. No matter what you
do :
-- If you press the power button from the case, it is the only answer that you
can get from the output display : it shows a console indicating that x-server
is trying to be turned off. But nothing else happens and the system can't be
turned off.
-- If you try anything from ssh : "init 0", "poweroff", "shutdown -P 0 -h",
"reboot". It simply does not work. It keeps waiting for something that never
happens. Then you have to press ctrl_c to get back to the ssh sessioon. In an
attempt it closed the ssh daemon but the shutdown itself never happened... even
after 30mins.
-- It is IMPOSSIBLE to force unload amdgpu using "rmmod -f amdgpu". The task
takes forever and never responds. It only hangs the ssh session.
-- It is IMPOSSIBLE to kill some x-related pids properly. If you try to kill it
either nothing will happen or the process will be in a defunct state. Not even
a "su -c 'kill -9 <pid>'" will work.
TIPS
- The crashes that allows ssh connection almost always happens when firefox is
openned and running a video (netflix, youtube) or whatsapp web.
- The crashes that simply hangs the entire computer may occur at any time.
OBSERVATIONS
- I use a custom kernel (from 4.15). I've tried including the polaris binaries
for my card, that showed an improvement (less freeze states) for a while. But
now it is the same again.
- I use a nvidia io second pci-e slot for vfio. It is a must and I disable
nouveau as well... It shoud not be a reason for failing. I tried also with
another amd/none-card on second slot. The results were the same as I remember.
SYSTEM SPECS
- Custom kernel compilation optimized for ryzen
(https://wiki.gentoo.org/wiki/Ryzen) and using polaris binaries
(https://wiki.gentoo.org/wiki/AMDGPU)
- Chipset X370 (mobo)
- RX480 in first slot
- GTX 1070 on second slot.
- Tried also with a RX 580 on second slot.
- Tried also with nothing on second slot.
- i3wm loading from startx command
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4949 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 reply other threads:[~2018-03-25 4:47 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 4:47 bugzilla-daemon [this message]
2018-03-25 4:49 ` [Bug 105733] Amdgpu randomly hangs and only ssh works. Mouse cursor moves sometimes but does nothing. Keyboard stops working 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
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@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.