Kernel bug #5047 - sata_sil w/ seagate drives

Kernel bug #5047 - sata_sil w/ seagate drives

[Stephan Arrington]

Hello,

I am also experiencing this behavior with sata_sil and large seagate  
drives.
Under heavy activity this bug surfaces (as mentioned in #5047) and it  
requires a reboot to fix.

Would adding the drive's firmware to the sil_blacklist [] be a  
possible workaround?

I am using kernel version 2.6.12-5.



///
  Vendor: ATA       Model: ST3300831AS       Rev: 3.02
///

///
00:0d.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/ 
SATARaid] Serial ATA Controller (rev 02)
         Subsystem: Silicon Image, Inc. SiI 3114 SATARaid Controller
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-  
ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium  
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 32, Cache Line Size 08
         Interrupt: pin A routed to IRQ 12
         Region 0: I/O ports at ac00 [size=8]
         Region 1: I/O ports at b000 [size=4]
         Region 2: I/O ports at b400 [size=8]
         Region 3: I/O ports at b800 [size=4]
         Region 4: I/O ports at bc00 [size=16]
         Region 5: Memory at e3047000 (32-bit, non-prefetchable)  
[size=1K]
         Capabilities: [60] Power Management version 2
                 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME 
(D0-,D1-,D2-,D3hot-,D3cold-)
                 Status: D0 PME-Enable- DSel=0 DScale=2 PME-
///

Thanks,
Stephan Arrington

Re: Kernel bug #5047 - sata_sil w/ seagate drives

[Tejun]

Hello, Stephan.

Stephan Arrington wrote:
> Hello,
> 
> I am also experiencing this behavior with sata_sil and large seagate  
> drives.
> Under heavy activity this bug surfaces (as mentioned in #5047) and it  
> requires a reboot to fix.
> 
> Would adding the drive's firmware to the sil_blacklist [] be a  possible 
> workaround?
> 
> I am using kernel version 2.6.12-5.
> 
> 
> 
> ///
>  Vendor: ATA       Model: ST3300831AS       Rev: 3.02
> ///
> 
> ///
> 00:0d.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/ 
> SATARaid] Serial ATA Controller (rev 02)
>         Subsystem: Silicon Image, Inc. SiI 3114 SATARaid Controller
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-  
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium  
>  >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 32, Cache Line Size 08
>         Interrupt: pin A routed to IRQ 12
>         Region 0: I/O ports at ac00 [size=8]
>         Region 1: I/O ports at b000 [size=4]
>         Region 2: I/O ports at b400 [size=8]
>         Region 3: I/O ports at b800 [size=4]
>         Region 4: I/O ports at bc00 [size=16]
>         Region 5: Memory at e3047000 (32-bit, non-prefetchable)  [size=1K]
>         Capabilities: [60] Power Management version 2
>                 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME 
> (D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=2 PME-
> ///
> 

Both your controller and drive are NOT the ones with m15w quirk.  My 
first suspects are bad cabling and/or bad controller.  Is the controller 
on board? or is it a discrete card?  Can you verify that earlier kernel 
doesn't show the error?  Do you happen to have another harddrive (maybe 
from a different manufacturer) which can be hooked to the controller and 
tested?

AFAICS, your problem doesn't seem to be m15w related.  In the past, we 
saw some cheap/flakey 3112 controllers which fail from time to time. 
libata sometimes fails to recover from such failures.  This might be 
what you're seeing.

-- 
tejun