[radeonsi, regression, bisected] All my Steam games fail to load into the 3D-engine-powered part (SIGPWR and SIGXCPU)

Alex Deucher alexdeucher at gmail.com
Mon Nov 17 08:58:30 PST 2014


On Sat, Nov 15, 2014 at 6:59 PM, Kai Wasserbäch
<kai at dev.carbon-project.org> wrote:
> Kai Wasserbäch wrote on 15.11.2014 22:22:
>> Kai Wasserbäch wrote on 15.11.2014 16:33:
>>> Is there anything besides a bisect you would need to debug this?
>>
>> Ok, I did a bisection, but that time was wasted for sure. My "first bad commit"
>> isn't bad at all. Is there any way to improve that experience? I'm really loathe
>> to go through the dozen boots again, just to get another broken bisection.
>
> Ok, after looking at the changes for radeon I decided to try the HEAD of
> drm-next-3.19 (c81b99423bd9d3fc35ac8752ca5fb4c50eab063c). That was still good.
> Armed with this much smaller bisection range, I came up with a result that
> sounds at least believable:
> 3cd76f3901e73a4a61d78c4526dcbf6d87c9a928 is the first bad commit
> commit 3cd76f3901e73a4a61d78c4526dcbf6d87c9a928
> Author: Christian König <christian.koenig at amd.com>
> Date:   Mon Oct 13 12:41:47 2014 +0200
>
>     drm/radeon: update the VM after setting BO address (v2)
>
>     This way the necessary VM update is kicked off immediately
>     if all BOs involved are in GPU accessible memory.
>
>     v2: fix vm lock handling
>
>     Signed-off-by: Christian König <christian.koenig at amd.com>
>     Signed-off-by: Alex Deucher <alexander.deucher at amd.com>
>
> :040000 040000 5bb1cc4497cc2e5b9af3a59170d7a8d5c99fd0a0
> 3df4996bc1a25f9275b833c778cdc33a30b28838 M      drivers
>
> CCing Christian, maybe he has an idea, what's up.
>
> Let me know, if you need something else, to debug this or if I should file this
> as a bug.
>
>
>> I noticed, however, that the following line is showing up with be762d181e in dmesg:
>> [drm:ci_dpm_init [radeon]] *ERROR* Invalid PCC GPIO!== power state 0 ==
>
> This seems to be unrelated as it shows up with all the commits from the 3.19
> branch, I've tested for this bisection run, even those, that worked. (Might this
> be, however, related to <https://bugs.freedesktop.org/show_bug.cgi?id=82201>?)
>

Yes, that is just some additional debugging output for dpm on newer
kernels.  It doesn't change anything from a hw perspective.

Alex

> Cheers,
> Kai
>


More information about the dri-devel mailing list