https://bugs.freedesktop.org/show_bug.cgi?id=110142

--- Comment #5 from Peter Easton <JollyRoger@Mailfence.com> ---

I'm going to try to see if I can narrow things down a bit by finding the last
commit that worked before the bug happened and then bisect the kernel there.
I'm going to try to compile the kernels, install them, and then try rebooting
and starting xfce4 one by one until I find the one that won't start.

I apologize in advance for the sluggishness, there are a lot of commits here
and the computer boots very slowly, so this puts a bit of a bottleneck on how
many kernels I can test in a given timeframe. I'll try to hurry as best I can
and I'll try to keep this thread updated as I make progress on it. Right now I
think I'll start at commit af0df68432f65915b2a316aa99eeeb588d4c65a2 since that
one works, and I'll start working my way towards 5.0.0 from there to see if I
can narrow down the right commit that borked the driver. 

> I guess the problem is actually in gmc_v9_0_allocate_vm_inv_eng though. Peter, what does...[truncated]

Sure. 5.0.2, which gave us that dmesg output, returned to this message when I
tried to enter the commands as followed, this is what the screen looks like: 

> captain@morgans-revenge /usr/src/linux-5.0.2-gentoo/scripts $ ./faddr2line ../drivers/gpu/drm/amd/amdgpu/amdgpu.ko
> gmc_v9_0_late_init+0x114/0x500
> gmc_v9_0_late_init+0x114/0x500:
> gmc_v9_0_late_init at gmc_v9_0.c:?
> captain@morgans-revenge /usr/src/linux-5.0.2-gentoo/scripts $

I hope this might be what you are looking for? I wasn't sure what to enter so I
looked for the drivers folder and then typed the rest in as it was.

-- 
You are receiving this mail because:
You are the assignee for the bug.