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] New: Recursive error in radeon device driver module after resume from hibernation
Date: Wed, 01 Apr 2015 00:49:27 +0000	[thread overview]
Message-ID: <bug-95911-2300@https.bugzilla.kernel.org/> (raw)

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

               URL: https://bugzilla.redhat.com/show_bug.cgi?id=1207874
            Bug ID: 95911
           Summary: Recursive error in radeon device driver module after
                    resume from hibernation
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.18.x and later
          Hardware: x86-64
                OS: Linux
              Tree: Fedora
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: gitne@excite.co.jp
        Regression: No

Created attachment 172841
  --> https://bugzilla.kernel.org/attachment.cgi?id=172841&action=edit
Kernel log

Description of problem:
Recursive error in radeon device driver module after resume from hibernation.
See attached kernel log for details.

Version-Release number of selected component (if applicable):
Linux 3.18.9-200.fc21.x86_64 #1 SMP Mon Mar 9 15:10:50 UTC 2015 x86_64 x86_64
x86_64 GNU/Linux (and later)

Steps to reproduce:
1. Run X.Org X Server 1.16.3 with radeon X.Org driver 7.5.0 (plus GNOME 3.14 or
whatever else you like) on AMD A10-7800 Radeon R7
2. Suspend to disk with i.e. "systemctl hibernate".
3. Resume from hibernation.

Actual results:
Current login session is killed and X.Org server recovers into AIGLX software
rendering.

Expected results:
No error in radeon device driver module.

Additional info:
See attached kernel log, cpuinfo, meminfo, and lspci. Booting with radeon
default kernel boot parameters.

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

             reply	other threads:[~2015-04-01  0:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01  0:49 bugzilla-daemon [this message]
2015-04-01  0:50 ` [Bug 95911] Recursive error in radeon device driver module after resume from hibernation 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
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@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).