so Intel acknowledged the issue we reported, and had two additional version commits since then.
For me, these still do not build, with the same error as reported back in August.
Intel verified and claims it is fixed and points to a 'custom' kernel.
Just to mention it again, the latest commit...