(In reply to Takashi Iwai from comment #1) > This doesn't sound like a kernel problem but rather the wrong request for a > device. Reassigned. My reasoning was that every block device has a valid block range (detected by the kernel) trying to read a block outside that range is not very likely to be successful (and thus should be avoided). What also made me think that it is a kernel problem is the masses of kernel messages being generated.