On 09/06/2016 05:36 PM, John Garry wrote:
> The endianness for the SAS address in the TX_ID_DWORD
> registers is set incorrectly.
> We see errors like this in the boot log for v2 hw (which would
> have the same issue as v1 hw):
> [7.583284] sas: target proto 0x0 at 5d1108e7923f:0x1f not
On 09/06/2016 05:36 PM, John Garry wrote:
> The endianness for the SAS address in the TX_ID_DWORD
> registers is set incorrectly.
> We see errors like this in the boot log for v2 hw (which would
> have the same issue as v1 hw):
> [7.583284] sas: target proto 0x0 at 5d1108e7923f:0x1f not
The endianness for the SAS address in the TX_ID_DWORD
registers is set incorrectly.
We see errors like this in the boot log for v2 hw (which would
have the same issue as v1 hw):
[7.583284] sas: target proto 0x0 at 5d1108e7923f:0x1f not handled
This is due to the host SAS addr not matching
The endianness for the SAS address in the TX_ID_DWORD
registers is set incorrectly.
We see errors like this in the boot log for v2 hw (which would
have the same issue as v1 hw):
[7.583284] sas: target proto 0x0 at 5d1108e7923f:0x1f not handled
This is due to the host SAS addr not matching
4 matches
Mail list logo
