More likely that whatever kernel call it is using has suffered a parameter change inside the (open-source) kernel. Like expecting a 64-bit value instead of a 32-bit value, or added/removed an extra parameter or some such thing. TONS of that kind of stuff happening almost daily in the 2.6 stream.

Cheers