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: Tue, 18 Aug 2015 07:23:34 +0000 [thread overview]
Message-ID: <bug-95911-2300-PaQTEZr27F@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 #19 from gitne@excite.co.jp ---
Just tested kernel version 4.1.4, and I have also started playing with some of
the radeon module parameters. It turns out that when I set radeon.msi=0
everything works as expected. No ring test failures anymore and hibernation
works perfect too. However, when I set radeon.msi to 1 or -1 (auto) I get
exactly the same behavior as described earlier.
As it turns out the message signaled interrupts code in the radeon device
driver module is broken. I have had similar behavior with the Radeon Mobility
2600 HD (R630). The difference was that hibernation worked but when radeon.msi
was set to 1 or -1 (auto) the radeon device driver module caused initially
seemingly random lockups, which over time, as interrupts got generated from
input devices, the lockups have been released for a couple hundred milliseconds
until another interrupt had to be handled by the radeon device driver module.
So, I would say that the message signaling interrupt code still needs some
major work.
--
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-08-18 7:23 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
2015-08-04 22:43 ` bugzilla-daemon
2015-08-18 7:23 ` bugzilla-daemon [this message]
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-PaQTEZr27F@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 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.