From: "Michel Dänzer" <michel@daenzer.net>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "Christian König" <christian.koenig@amd.com>,
DRI <dri-devel@lists.freedesktop.org>
Subject: Re: Long radeon stalls on recent kernels
Date: Wed, 19 Nov 2014 16:19:09 +0900 [thread overview]
Message-ID: <546C446D.9000505@daenzer.net> (raw)
In-Reply-To: <CALCETrW0-WdYHbSEpVCiL1dUS-_c_3T5ZMMYdSL__HHDOcB6Ag@mail.gmail.com>
On 19.11.2014 09:21, Andy Lutomirski wrote:
> On Mon, Nov 17, 2014 at 1:51 AM, Michel Dänzer <michel@daenzer.net> wrote:
>> On 15.11.2014 07:21, Andy Lutomirski wrote:
>>>
>>> On recent kernels (3.16 through 3.18-rc4, perhaps), doing anything
>>> graphics intensive seems to cause my system to become unusable for
>>> tens of seconds. Pointing Firefox at Google Maps is a big offender --
>>> it can take several minutes for me to move my mouse far enough to
>>> close the tab and get my computer back.
>>>
>>> On bootup, I get this warning:
>>> [drm:btc_dpm_set_power_state] *ERROR*
>>> rv770_restrict_performance_levels_before_switch failed
>>>
>>> Setting radeon.dpm=0 seems to work around this problem at the cost of
>>> giving my rather slow graphics.
>>>
>>> Are there known issues here?
>>
>>
>> Can you bisect the kernel, or at least isolate which kernel version first
>> introduced the problem?
>
> With whatever userspace I'm running, I'm seeing it 3.13, 3.14, 3.15,
> 3.16, and 3.18-rc4+. I haven't tried other versions.
>
> With radeon.dpm=0, I can still trigger short stalls (around one
> second), but I seem unable to trigger long stalls easily. (I say
> easily because, just as I was typing this email, my system stalled for
> about a minute.)
I can only think of two things offhand that could cause such extremely
long stalls: Swap thrashing or IRQ storms.
With a setup where you can easily trigger long stalls, can you try
getting a CPU profile for a stall with sysprof or perf?
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-11-19 7:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 22:21 Long radeon stalls on recent kernels Andy Lutomirski
2014-11-17 9:51 ` Michel Dänzer
2014-11-19 0:21 ` Andy Lutomirski
2014-11-19 0:34 ` Andy Lutomirski
2014-11-19 0:50 ` Andy Lutomirski
2014-11-19 7:19 ` Michel Dänzer [this message]
2014-11-20 0:07 ` Andy Lutomirski
2014-11-20 0:58 ` Andy Lutomirski
2014-11-26 6:42 ` Michel Dänzer
2014-11-26 15:38 ` Andy Lutomirski
2014-12-09 0:24 ` Andy Lutomirski
2014-12-09 9:18 ` Michel Dänzer
2014-12-09 16:06 ` Andy Lutomirski
2014-12-09 21:39 ` Andy Lutomirski
2014-12-10 9:44 ` Michel Dänzer
2014-12-10 20:28 ` Andy Lutomirski
2014-12-11 4:24 ` Michel Dänzer
2014-12-11 5:13 ` Andy Lutomirski
2014-12-16 8:00 ` Michel Dänzer
2014-12-10 14:56 ` Alex Deucher
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=546C446D.9000505@daenzer.net \
--to=michel@daenzer.net \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=luto@amacapital.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