LibATA error

LibATA error

[Lukas Hejtmanek]

Hello,

what does the following error mean? Does it mean that my shiny new SSD is
buggy?

[  461.382432] ata1.00: exception Emask 0x2 SAct 0x1 SErr 0x2000000 action 0x6
frozen
[  461.382484] ata1.00: irq_stat 0x00000010, unknown FIS 00000000 00000000
00000000 00000000
[  461.382534] ata1: SError: { UnrecFIS }
[  461.382572] ata1.00: cmd 61/08:00:0f:82:de/00:00:00:00:00/40 tag 0 ncq 4096
out
[  461.382574]          res 40/00:00:0f:82:de/00:00:00:00:00/40 Emask 0x2 (HSM
violation)
[  461.382666] ata1.00: status: { DRDY }
[  461.382702] ata1: hard resetting link
[  461.700087] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

-- 
Lukáš Hejtmánek

Re: LibATA error

[Robert Hancock]

Lukas Hejtmanek wrote:
> Hello,
> 
> what does the following error mean? Does it mean that my shiny new SSD is
> buggy?
> 
> [  461.382432] ata1.00: exception Emask 0x2 SAct 0x1 SErr 0x2000000 action 0x6
> frozen
> [  461.382484] ata1.00: irq_stat 0x00000010, unknown FIS 00000000 00000000
> 00000000 00000000
> [  461.382534] ata1: SError: { UnrecFIS }
> [  461.382572] ata1.00: cmd 61/08:00:0f:82:de/00:00:00:00:00/40 tag 0 ncq 4096
> out
> [  461.382574]          res 40/00:00:0f:82:de/00:00:00:00:00/40 Emask 0x2 (HSM
> violation)
> [  461.382666] ata1.00: status: { DRDY }
> [  461.382702] ata1: hard resetting link
> [  461.700087] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> 

It could be.. it means the drive sent the controller a SATA FIS (frame 
information structure) it didn't recognize.

Re: LibATA error

[Lukas Hejtmanek]

On Sat, Dec 06, 2008 at 02:29:19PM -0600, Robert Hancock wrote:
>> [  461.382432] ata1.00: exception Emask 0x2 SAct 0x1 SErr 0x2000000 action 0x6
>> frozen
>> [  461.382484] ata1.00: irq_stat 0x00000010, unknown FIS 00000000 00000000
>> 00000000 00000000
>> [  461.382534] ata1: SError: { UnrecFIS }
>> [  461.382572] ata1.00: cmd 61/08:00:0f:82:de/00:00:00:00:00/40 tag 0 ncq 4096
>> out
>> [  461.382574]          res 40/00:00:0f:82:de/00:00:00:00:00/40 Emask 0x2 (HSM
>> violation)
>> [  461.382666] ata1.00: status: { DRDY }
>> [  461.382702] ata1: hard resetting link
>> [  461.700087] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>>
>
> It could be.. it means the drive sent the controller a SATA FIS (frame  
> information structure) it didn't recognize.

hm, if I disable NCQ, I do not get these errors. Maybe OCZ SSD disks should be
blacklisted for NCQ?

-- 
Lukáš Hejtmánek

Re: LibATA error

[Alan Cox]

> > It could be.. it means the drive sent the controller a SATA FIS (frame  
> > information structure) it didn't recognize.
> 
> hm, if I disable NCQ, I do not get these errors. Maybe OCZ SSD disks should be
> blacklisted for NCQ?

They shouldn't be claiming they can do NCQ if so. Can you dump out the
identify data in full (with hdparm) and if possible (or if someone else
with one can comment..) find out whether the same occurs with different
controller types.

Alan

Re: LibATA error

[Lukas Hejtmanek]

On Sun, Dec 07, 2008 at 06:36:47PM +0000, Alan Cox wrote:
> They shouldn't be claiming they can do NCQ if so. Can you dump out the
> identify data in full (with hdparm) and if possible (or if someone else
> with one can comment..) find out whether the same occurs with different
> controller types.

Controller reports NCQ queue depth 1.

Did you mean this one?

 hdparm -i /dev/sda

/dev/sda:

 Model=OCZ CORE_SSD                            , FwRev=02.10104,
SerialNo=DC030849085600010   
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=63
 BuffType=unknown, BuffSize=0kB, MaxMultSect=1, MultSect=?1?
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=504856576
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: unknown:  ATA/ATAPI-1,2,3,4,5,6,7

 * signifies the current active mode

-- 
Lukáš Hejtmánek