From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95911] Recursive error in radeon device driver module after resume from hibernation
Date: Mon, 08 Jun 2015 23:05:34 +0000 [thread overview]
Message-ID: <bug-95911-2300-d3SWIsvvPG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-95911-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=95911
--- Comment #17 from gitne@excite.co.jp ---
(In reply to Alex Deucher from comment #16)
> Created attachment 178141 [details]
> possible fix
>
> Does the attached patch help?
Thank you for proposing a possible solution. Unfortunately, I do not know if
this patch is going to help because I am not a kernel developer. I do not build
nor intend to build any kernels. However, I can test fully functional Fedora
RPM packages.
Nevertheless, I have tested kernel version 3.19.7. As it turns out, hibernation
and wake up seem to work properly if no Firefox is running. Latest versions of
Firefox always use some sort of hardware accelerated graphics. This makes me
assume that the radeon device driver (or the device itself) is put into some
inconsistent or invalid state from user-space, meaning, input values to
kernel-space are not checked properly by the device driver. This invalid state
can probably be saved but cannot be restored on wake up because it is - well -
invalid by definition. So, although I am not a kernel developer I pretty much
doubt that the proposed patch is going to fix this problem because it seems to
put the device just into a deeper sleep mode. This change has no impact on any
previously saved invalid state, regardless while saving or while restoring.
But, as always, I may be wrong.
Can you build a test package?
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-06-08 23:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 0:49 [Bug 95911] New: Recursive error in radeon device driver module after resume from hibernation bugzilla-daemon
2015-04-01 0:50 ` [Bug 95911] " bugzilla-daemon
2015-04-01 0:53 ` bugzilla-daemon
2015-04-01 0:54 ` bugzilla-daemon
2015-04-01 0:54 ` bugzilla-daemon
2015-04-01 0:55 ` bugzilla-daemon
2015-04-01 0:57 ` bugzilla-daemon
2015-04-01 2:13 ` bugzilla-daemon
2015-04-27 11:36 ` bugzilla-daemon
2015-04-30 9:25 ` bugzilla-daemon
2015-04-30 9:59 ` bugzilla-daemon
2015-04-30 11:51 ` bugzilla-daemon
2015-05-01 0:56 ` bugzilla-daemon
2015-05-01 6:41 ` bugzilla-daemon
2015-05-06 16:39 ` bugzilla-daemon
2015-05-07 1:17 ` bugzilla-daemon
2015-05-12 13:59 ` bugzilla-daemon
2015-05-27 19:26 ` bugzilla-daemon
2015-06-08 23:05 ` bugzilla-daemon [this message]
2015-08-04 22:43 ` bugzilla-daemon
2015-08-18 7:23 ` bugzilla-daemon
2015-08-18 15:01 ` bugzilla-daemon
2015-08-19 2:53 ` bugzilla-daemon
2015-08-19 2:57 ` bugzilla-daemon
2015-09-02 23:57 ` 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-95911-2300-d3SWIsvvPG@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 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).