I'm going to try to see if I can narrow things down a bit by finding the la=
st
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 rebooti=
ng
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 h=
ow
many kernels I can test in a given timeframe. I'll try to hurry as best I c=
an
and I'll try to keep this thread updated as I make progress on it. Right no=
w I
think I'll start at commit af0df68432f65915b2a316aa99eeeb588d4c65a2 since t=
hat
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.=20

> I guess the problem is actually in gmc_v9_0_allo=
cate_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=
:=20

> 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.