From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65761] HD 7970M Hybrid - hangs and errors and rmmod causes crash
Date: Tue, 21 Jan 2014 00:15:48 +0000 [thread overview]
Message-ID: <bug-65761-2300-KvWnbK1gvI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65761-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=65761
Christoph Haag <haagch.christoph@googlemail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #115961|0 |1
is obsolete| |
Attachment #119501|0 |1
is obsolete| |
Attachment #119551|0 |1
is obsolete| |
--- Comment #15 from Christoph Haag <haagch.christoph@googlemail.com> ---
Created attachment 122811
--> https://bugzilla.kernel.org/attachment.cgi?id=122811&action=edit
erratic dpm with window manager actions
Okay, so we got 3.13 without crashes with default settings, so far so good,
thanks so much. :)
The dynpm power management is wonky. It doesn't really fit in here, but I
already dumped a lot of stuff in here anyway and this report has been linked to
in relation to me mentioning that the power management isn't working well yet,
so here is another (not so) small point.
Here is a screenshot from the tool radeon-profile. I believe over the whole
period shown there I have not used the radeon GPU to render anything, but it is
configured as offload slave. I also hope that this tool did not cause this
behaviour, but from the fan noise I think it's happening without it too.
So there are some random "short" spikes that die off after a while of doing
nothing in X. However there are these longer spikes (about 5-7 seconds) when
doing some window management actions. An example of that is
minimizing/unminizing a window or simply changing the focus from one window to
another window via the mouse. I have tested this with kwin with compositing and
openbox without compositing and I think it's pretty clear that this actually
causes it. Changing tabs in chromium also seems to cause it.
The very quick spikes happened when I additionally ran glxgears with kwin
(still everything on the Intel GPU). They died down but appeared sometimes
again after doing something with the windows. With openbox on the other hand I
don't see such quick spikes with glxgears.
Another funny effect in openbox is that a single click on the "gears" in
glxgears doesn't have an effect, but a double click produces one of the longer
spikes. If I single click in chromium here in the bugtracker on the bakground
or in the textarea it produces a spike too. But simply typing in the textarea
does not.
I don't really know what to make of those observations, but I would guess that
the radeon gpu doesn't enter the dynoff state while X is running because of
something related to this. A short google search didn't show anything new about
radeonsi + dynoff, especially nobody who claims it's working, so maybe glamor
is worth looking at?
The intel gpu uses SNA and radeon obviously glamor. If the Xorg.0.log or so
would be helpful, just ask.
Maybe someone with a pre radeonsi gpu could test whether they have the same
issue when using glamor over exa?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-01-21 0:15 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 16:49 [Bug 65761] New: HD 7970M Hybrid - hangs and errors and rmmod causes crash bugzilla-daemon
2013-11-25 17:15 ` [Bug 65761] " bugzilla-daemon
2013-11-26 20:03 ` bugzilla-daemon
2013-11-30 12:12 ` bugzilla-daemon
2013-12-06 22:21 ` bugzilla-daemon
2013-12-06 22:34 ` bugzilla-daemon
2013-12-07 1:06 ` bugzilla-daemon
2013-12-07 1:17 ` bugzilla-daemon
2013-12-24 15:45 ` bugzilla-daemon
2013-12-24 19:43 ` bugzilla-daemon
2013-12-24 19:45 ` bugzilla-daemon
2013-12-24 21:40 ` bugzilla-daemon
2014-01-06 11:57 ` bugzilla-daemon
2014-01-06 21:52 ` bugzilla-daemon
2014-01-19 23:22 ` bugzilla-daemon
2014-01-21 0:15 ` bugzilla-daemon [this message]
2014-01-21 0:23 ` bugzilla-daemon
2014-01-21 0:55 ` bugzilla-daemon
2014-01-21 21:58 ` bugzilla-daemon
2014-01-22 1:53 ` bugzilla-daemon
2014-01-22 1:53 ` bugzilla-daemon
2014-01-22 1:53 ` bugzilla-daemon
2014-01-24 2:20 ` bugzilla-daemon
2014-01-31 0:10 ` bugzilla-daemon
2014-01-31 14:14 ` bugzilla-daemon
2014-01-31 20:00 ` bugzilla-daemon
2014-01-31 20:46 ` bugzilla-daemon
2014-01-31 21:24 ` bugzilla-daemon
2014-01-31 23:00 ` bugzilla-daemon
2014-02-01 0:08 ` bugzilla-daemon
2014-02-02 23:58 ` bugzilla-daemon
2014-02-06 13:48 ` bugzilla-daemon
2014-02-07 0:49 ` bugzilla-daemon
2014-02-07 14:52 ` bugzilla-daemon
2014-02-07 22:39 ` bugzilla-daemon
2014-02-07 22:44 ` bugzilla-daemon
2014-02-07 22:47 ` bugzilla-daemon
2014-02-11 1:58 ` bugzilla-daemon
2014-02-11 7:30 ` bugzilla-daemon
2014-02-12 7:55 ` bugzilla-daemon
2014-02-12 9:41 ` bugzilla-daemon
2014-02-13 2:53 ` bugzilla-daemon
2014-02-13 9:00 ` bugzilla-daemon
2014-02-13 12:12 ` bugzilla-daemon
2014-02-14 2:59 ` bugzilla-daemon
2014-02-15 17:33 ` bugzilla-daemon
2014-02-17 17:04 ` bugzilla-daemon
2014-02-19 0:45 ` bugzilla-daemon
2014-02-19 0:46 ` bugzilla-daemon
2014-02-19 1:26 ` bugzilla-daemon
2014-02-19 2:45 ` bugzilla-daemon
2014-03-03 0:19 ` bugzilla-daemon
2014-03-03 0:20 ` bugzilla-daemon
2014-03-03 8:22 ` bugzilla-daemon
2014-03-03 23:16 ` bugzilla-daemon
2014-03-03 23:25 ` bugzilla-daemon
2014-04-01 9:00 ` bugzilla-daemon
2015-01-04 1:09 ` 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-65761-2300-KvWnbK1gvI@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 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).