> That could be a plymouth bug. I've noticed that it doesn't seem to call
> drmModeCrtcSetGamma to make sure the display CLUTs are initialized to
> appropriate values.

Yeah, it could be, I'll investigate the plymouth issue later, right now the
kernel panic situation is the top priority on my list :D

Any idea what's triggering the stack corruption? I'm still investigating but
right now my bet is on casting args to (uint32_t *) in

amdgpu_atom_execute_table(adev->mode_info.atom_context, index, (uint32_t
*)&args);