I filed this bug report about 'failed to get NCQ Send/Recv Log Emask 0x1';
Now I see this in my DMESG for 4.1.6;
READ LOG DMA EXT failed, trying unqueued
I don't know if there is a relation here, meaning, unsupported device with my Samsung 850 Pro 128GB SSD?
I think it is the firmware, a similiar question came up on a SAMSUNG SSD 840 EVO.
Reporter updated firmware and the failure disappeared.
Here is link to upstream discussion, thanks.
The 850 Pro does not have any firmware updates at this time...
In the meantime I'm wondering if I'm going to run into any problems?
Found this patch, not sure if I should apply it;
(In reply to KernelBug from comment #2)
> The 850 Pro does not have any firmware updates at this time...
> In the meantime I'm wondering if I'm going to run into any problems?
I don't think so, it should be falling back to ATA_CMD_READ_LOG_EXT.
> Found this patch, not sure if I should apply it;
You can, it was committed. Thanks.
libata: Fix regression when the NCQ Send and Receive log page is absent
Commited, what do you mean? It's going to end up in the kernel later?
It seems to of been applied already, I'm using 4.1.6
So if the patch has already been added in, is it stil normal to get this msg?
Is this some hardware error that will cause problems, or is this a failure to read a log?
Even with the patch applied (Comment#3), it won't get rid of the message,
but it will keep you from spinning in "READ LOG DMA EXT failed, trying
unqueued", I don't think it will cause you any more errors. The problem is
the drive advertises that it supports the DMA variant of READ LOG EXT, but
it really doesn't so driver falls back. Thanks.