Agree completely, Gav Mack. Seems likely to me to be a regression in the kernal that should be fixed. Unfortunately, it looks like the associated kernal bug (#14583) is being put down to dodgy hardware.
The libata.dma=<4 is just a workaround to keep us up and running in the interim... if you can put up with the negative impact on performance :)
Agree completely, Gav Mack. Seems likely to me to be a regression in the kernal that should be fixed. Unfortunately, it looks like the associated kernal bug (#14583) is being put down to dodgy hardware.
The libata.dma=<4 is just a workaround to keep us up and running in the interim... if you can put up with the negative impact on performance :)