From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16180] New: radeon regression with 2.6.35-rc2-00001-g386f40c: black screen after resume
Date: Fri, 11 Jun 2010 10:59:25 GMT [thread overview]
Message-ID: <bug-16180-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=16180
Summary: radeon regression with 2.6.35-rc2-00001-g386f40c:
black screen after resume
Product: Drivers
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: cedric@belbone.be
Regression: Yes
With the aforementioned kernel version, after a resume the screen stays black.
Everything seems responding (wifi led blinking, reboot, ...).
After reading the logs between this kernel and 2.6.35-rc1-00194-gaef4b9a (known
good), i think the problem is with this patch
drm/radeon/kms: make sure display hw is disabled when suspending
After I did apply the attached patch, the resume seems OK.
Don't know if it's the good solution...
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
--
next reply other threads:[~2010-06-11 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 10:59 bugzilla-daemon [this message]
2010-06-11 11:03 ` [Bug 16180] radeon regression with 2.6.35-rc2-00001-g386f40c: black screen after resume bugzilla-daemon
2010-06-11 16:06 ` bugzilla-daemon
2010-06-11 18:24 ` bugzilla-daemon
2010-06-11 18:41 ` bugzilla-daemon
2010-06-14 20:02 ` bugzilla-daemon
2010-07-08 22:48 ` 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-16180-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox