From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66473] New: hdmi oops with mem sleep
Date: Mon, 01 Jul 2013 21:58:13 +0000 [thread overview]
Message-ID: <bug-66473-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1161 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66473
Priority: medium
Bug ID: 66473
Assignee: dri-devel@lists.freedesktop.org
Summary: hdmi oops with mem sleep
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: adf.lists@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 81834
--> https://bugs.freedesktop.org/attachment.cgi?id=81834&action=edit
oops hdmi
RV790 running drm-next as it was on 260613
Have used echo mem > /sys/power/state for some time now, though I don't think
this is a regression - just a situation that I haven't hit before.
Haven't tested every senario but it seems that if I boot and use single DVI
monitor then someone else turns on TV which is connected DVI -> hdmi then if I
use mem sleep I get an oops. If the TV is on already when I boot it doesn't
happen. I am not enabling the TV with xrandr as it's not me that is using it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2556 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-07-01 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 21:58 bugzilla-daemon [this message]
2013-07-03 14:09 ` [Bug 66473] hdmi oops with mem sleep bugzilla-daemon
2013-07-06 8:59 ` bugzilla-daemon
2013-07-06 9:03 ` [Bug 66473] rv790 oops when switching to fbcon after resume from sleep after hdmi became active bugzilla-daemon
2013-10-30 20:33 ` 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-66473-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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).