All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100979] Radeon r4 on a6-6310(BEEMA) APU hard lockup on hibernate and on second resume from suspend
Date: Wed, 31 Jan 2018 10:55:44 +0000	[thread overview]
Message-ID: <bug-100979-502-gCXGpyXzKa@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100979-502@http.bugs.freedesktop.org/>


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

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

--- Comment #9 from Przemek <soprwa@gmail.com> ---
I have just upgraded kernel to 4.15.
There is a big progress. Laptop can now successfully suspend (S3) and resume 
many times in a row.

_Thank you very much for your hard work_.

But unfortunately hibernate to disk (S4) still does not work as expected.
Process is causing hard lockup (system freeze) just on the first attempt. 

Display goes black (backlight is on), cpu is getting hot (fans are working 100%
rpms), and I can do noting more than press "power button" to hard reset the
machine.

There is no more "amdgpu_atombios_dp_link_train" message in dmesg instead there
are mesages related to "swiotlb buffer is full" and "swiotlb: coherent
allocation failed" as in the bug:
https://bugs.freedesktop.org/show_bug.cgi?id=104082.

Thanks,
Przemek

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

[-- Attachment #1.2: Type: text/html, Size: 2023 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-01-31 10:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 21:11 [Bug 100979] Radeon r4 on a6-6310(BEEMA) APU hard lockup on hibernate and on second resume from suspend bugzilla-daemon
2017-05-09 21:12 ` bugzilla-daemon
2017-05-09 21:13 ` bugzilla-daemon
2017-05-09 21:14 ` bugzilla-daemon
2017-05-09 21:15 ` bugzilla-daemon
2017-05-09 21:17 ` bugzilla-daemon
2017-06-02 15:33 ` bugzilla-daemon
2017-06-28  8:58 ` bugzilla-daemon
2017-07-03 16:07 ` bugzilla-daemon
2018-01-31 10:55 ` bugzilla-daemon [this message]
2018-01-31 11:29 ` bugzilla-daemon
2018-01-31 12:12 ` bugzilla-daemon
2018-02-06 23:30 ` bugzilla-daemon
2018-03-28 10:54 ` bugzilla-daemon
2019-02-15 15:10 ` bugzilla-daemon
2019-02-16  9:20 ` 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-100979-502-gCXGpyXzKa@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.