All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198551] amdgpu error on shutdown or gpu intense game
Date: Thu, 21 Jun 2018 06:51:27 +0000	[thread overview]
Message-ID: <bug-198551-2300-f1Xd1shpPm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198551-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198551

Alex (linuxale@libero.it) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |linuxale@libero.it

--- Comment #3 from Alex (linuxale@libero.it) ---
I had a similar problem on a Dell Latitude E5470.
I had the follow error in the logs once reboot the system after a suspend:

Jun 21 07:50:57 sabayon kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios
stuck in loop for more than 5secs aborting
Jun 21 07:50:57 sabayon kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]]
*ERROR* atombios stuck executing 73EA (len 272, WS 0, PS 4) @ 0x7433
Jun 21 07:50:57 sabayon kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]]
*ERROR* atombios stuck executing 6036 (len 70, WS 0, PS 8) @ 0x605C
Jun 21 07:50:57 sabayon kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR*
amdgpu asic init failed


And the X never came back to life.

The trick as suggested above was to disable the amdgpu Power Management

GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.runpm=0"

Now suspend and hibernate works like a charm!.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-06-21  6:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 23:20 [Bug 198551] New: amdgpu error on shutdown or gpu intense game bugzilla-daemon
2018-01-27  6:58 ` [Bug 198551] " bugzilla-daemon
2018-02-11 22:12 ` bugzilla-daemon
2018-02-11 22:13 ` bugzilla-daemon
2018-06-21  6:51 ` bugzilla-daemon [this message]
2020-09-24 11:39 ` bugzilla-daemon
2024-01-05  9:49 ` bugzilla-daemon
2024-01-19  3:32 ` bugzilla-daemon
2024-01-22 10:15 ` 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-198551-2300-f1Xd1shpPm@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.