From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27086] New: radeon pm should have uninitialize function for cleaning pm state
Date: Mon, 15 Mar 2010 08:23:39 -0700 (PDT) [thread overview]
Message-ID: <bug-27086-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=27086
Summary: radeon pm should have uninitialize function for cleaning
pm state
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: suokkos@gmail.com
Currently unloading radeon module if dynpm is enabled causes oopses. It also
looks that if only fixing oopses radeon would leave card to power save mode.
When kernel module is unloaded power management should unregister the delayed
work with cancel_delayed_work_sync and set default power state.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-03-15 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 15:23 bugzilla-daemon [this message]
2010-03-15 15:49 ` [Bug 27086] radeon pm should have uninitialize function for cleaning pm state bugzilla-daemon
2010-03-15 15:58 ` bugzilla-daemon
2010-03-15 16:00 ` bugzilla-daemon
2010-03-17 2:35 ` bugzilla-daemon
2011-11-13 17:09 ` bugzilla-daemon
2014-01-23 11:51 ` 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-27086-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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.