In this case it was a driver holding that thread captive and making an assumption about the hardware eventually responding to a request which never completes.

So yes indeed it was the kernel, and ideally the driver could be written better, but that’s probably easier said than done when the hardware can do weird things.

This was a long time ago, so for all I know the issue has been long corrected.