dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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, 27 Apr 2015 11:36:51 +0000	[thread overview]
Message-ID: <bug-95911-2300-elpoWIyYKy@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 #7 from gitne@excite.co.jp ---
(In reply to Michel Dänzer from comment #6)
> Is this a regression compared to older kernel versions? If yes, can you
> bisect or at least narrow down which kernel version is the last good / first
> bad one?

Unfortunately, I cannot tell if this bug is a regression or new. I have started
to experience this bug only with my new piece of hardware AMD Radeon R7. I have
not tested specifically on a range different kernel versions either, nor intend
to bisect anything. Sorry, but I am using my machine to do actual work and do
not have time to do this kind of testing nor have the required knowledge to
compile the kernel. So no, I am not a kernel developer. If I were, I would
probably fix this and submit a patch but I am not.

The AMD APU Radeon R7 should be a common piece of hardware by now, and very
similar to any other APU Radeon R* so testing should be relatively easy for
kernel developers.

All I can say is that I have went through all the F21 kernel versions with the
same annoying effect. Since, Fedora kernel versions are somewhat lagging a bit
behind the upstream kernel versions, and hibernation not being a No. 1 test
feature, plus the R7 being a relatively new piece of hardware makes me assume
that this has not been fixed in the latest kernel versions either. I would
really love hibernation to work because it is a very practical and time saving
feature.

-- 
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

  parent reply	other threads:[~2015-04-27 11:36 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 [this message]
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
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-elpoWIyYKy@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).