I took the recently released kernel 4.19 as an incentive to test this again and
it looks like the issue is gone. I do, however, not know if it is indeed the
new kernel driver part or a mesa/LLVM update that happened in the meantime (I
did not test it after every update).