From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26781] New: RV670 Oops with PM and xrandr.
Date: Fri, 26 Feb 2010 15:12:43 -0800 (PST) [thread overview]
Message-ID: <bug-26781-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26781
Summary: RV670 Oops with PM and xrandr.
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: lists@andyfurniss.entadsl.com
Running current drt + pm patch in
http://bugs.freedesktop.org/show_bug.cgi?id=26631
While changing res with xrandr today I got a PM Oops, I can't reproduce so
maybe it tried to switch power just as xrandr was changing res. There is an
added complication that I was testing xrandr due to an issue I have with it -
http://bugs.freedesktop.org/show_bug.cgi?id=24532
so it may have been in a non normal state at the time.
While grepping my logs for the details, I noticed that it has happened before
and this case is reproducible - If I modprobe radeon without first loading
fbcon, startx, when I quit X I will get the Oops.
--
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-02-26 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 23:12 bugzilla-daemon [this message]
2010-02-26 23:13 ` [Bug 26781] RV670 Oops with PM and xrandr bugzilla-daemon
2010-03-15 13:58 ` bugzilla-daemon
2010-03-15 15: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-26781-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.