To save us some headache, CLContext.createBuffer fails if the source buffer's byte order is different from the OpenCL byte order.
If there is a byte order mismatch, the exception message refers to the deprecated getKernelsDefaultByteOrder(); it should be updated to getByteOrder().
A lesser annoyance is that I was greeted with this exception when using a byte pointer. If it's possible, it'd be nice if the byte order check were skipped for Pointer data, since there it doesn't matter.