From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97838] Hang on resume [AMD/ATI] RV515/M54 [Mobility Radeon X1400]
Date: Mon, 19 Sep 2016 15:06:31 +0000 [thread overview]
Message-ID: <bug-97838-502-IcItCcie1o@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97838-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 813 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97838
--- Comment #2 from Nikolay <mar.kolya@gmail.com> ---
Hi.
Thanks for your response!
It is somewhat hard because it goes from 'hangs almost always' on ubuntu's
4.4.0 kernel to 'hangs every time' on 4.7.3.
Also I assume xorg and its version may play some role in that because it
doesn't happen in text console.
It also looks like that there is some sort of dependency on how log it was off
- 4.4.0 almost never wakes up overnight.
I'll try to play with different versions to see if I can find a pattern...
I was hoping that there is some way to delay radeon awakening for after I get
net and can tail debug logs - so if there are errors it would dump them.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1607 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:[~2016-09-19 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 3:36 [Bug 97838] Hang on resume [AMD/ATI] RV515/M54 [Mobility Radeon X1400] bugzilla-daemon
2016-09-19 14:54 ` bugzilla-daemon
2016-09-19 15:06 ` bugzilla-daemon [this message]
2019-11-19 9:18 ` 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-97838-502-IcItCcie1o@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).