Maxtor 6L200M0 sata irq timeouts

Maxtor 6L200M0 sata irq timeouts

[Michal Suchanek]

Hello

(please CC me when replying)

I gott this drive connected to the sata controler (it's the only
drive, the other two ata buses are pata):

 Model=Maxtor 6L200M0                          , FwRev=BANC1E00
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=?16?
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
 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=yes: disabled (255) WriteCache=enabled
 Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0:  ATA/ATAPI-1,2,3,4,5,6,7

ata3.00: ATA-7: Maxtor 6L200M0, BANC1E00, max UDMA/133
ata3.00: 398297088 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133

Note: I beleive here the reports of dmesg and hdparm diverge. iirc
udma/133 is udma6.

FIrst I got a board with via chipset, and when it died I replaced it
with one with intel chipset.
The problem was there probably for a long time and went unnoticed
until the via board started dying and I looked into the logs. It
usually manifested while playing video that required something between
95% and 115% of the available cpu power to decode properly so I
assumed it is just mplayer catching up with realtime.

I get resets like this from time to time:

Sep  8 16:44:08 heretic ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0
action 0x2 frozen
Sep  8 16:44:08 heretic ata3.00: cmd
b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
Sep  8 16:44:08 heretic res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask
0x4 (timeout)
Sep  8 16:44:08 heretic ata3: soft resetting port
Sep  8 16:44:08 heretic ata3.00: configured for UDMA/133
Sep  8 16:44:08 heretic ata3: EH complete
Sep  8 16:44:08 heretic sd 2:0:0:0: [sda] 398297088 512-byte hardware
sectors (203928 MB)
Sep  8 16:44:08 heretic sd 2:0:0:0: [sda] Write Protect is off
Sep  8 16:44:08 heretic sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
Sep  8 16:44:08 heretic sd 2:0:0:0: [sda] Write cache: enabled, read
cache: enabled, doesn't support DPO or FUA

These are only noticable vhen doing realtime stuff like video playback.

When playing with stuff like noapic or pci=routeirq earlier I got
crashes instead of ata resets (there is not much you can do with a
system where the only drive gets disconnected, even if it does not
panic right away). With some combination of these I got a spurious
interrupt instead of timeout.

Thanks

Michal

Re: Maxtor 6L200M0 sata irq timeouts

[Michal Suchanek]

Hello

(please CC me when replying)

On 09/09/2007, Joris <joris@v5.be> wrote:
> Hi,
>
> Just a note to let you know you're not alone.
> I have the same problem, and someone else reported something simelar.
>
> What sata controller are you using?

The via onboard controller on the via chipset board and the Intel ICH7
integrated controller with this board. Looks like it is the drive and
the used controller does not make any difference.

00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family)
Serial ATA Storage Controller IDE (rev 01)

Thanks

Michal

Re: Maxtor 6L200M0 sata irq timeouts

[Tejun Heo]

Michal Suchanek wrote:
> Hello
> 
> (please CC me when replying)
> 
> On 09/09/2007, Joris <joris@v5.be> wrote:
>> Hi,
>>
>> Just a note to let you know you're not alone.
>> I have the same problem, and someone else reported something simelar.
>>
>> What sata controller are you using?
> 
> The via onboard controller on the via chipset board and the Intel ICH7
> integrated controller with this board. Looks like it is the drive and
> the used controller does not make any difference.
> 
> 00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family)
> Serial ATA Storage Controller IDE (rev 01)

What does 'smartctl -a /dev/sda' say?

-- 
tejun

Re: Maxtor 6L200M0 sata irq timeouts

[Michal Suchanek]

[-- Attachment #1: Type: text/plain, Size: 768 bytes --]

On 10/09/2007, Tejun Heo <htejun@gmail.com> wrote:
> Michal Suchanek wrote:
> > Hello
> >
> > (please CC me when replying)
> >
> > On 09/09/2007, Joris <joris@v5.be> wrote:
> >> Hi,
> >>
> >> Just a note to let you know you're not alone.
> >> I have the same problem, and someone else reported something simelar.
> >>
> >> What sata controller are you using?
> >
> > The via onboard controller on the via chipset board and the Intel ICH7
> > integrated controller with this board. Looks like it is the drive and
> > the used controller does not make any difference.
> >
> > 00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family)
> > Serial ATA Storage Controller IDE (rev 01)
>
> What does 'smartctl -a /dev/sda' say?
>
Attaching output.

Thanks

Michal

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: smartctl.log --]
[-- Type: text/x-log; name="smartctl.log", Size: 8035 bytes --]

smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family:     Maxtor DiamondMax 10 family (ATA/133 and SATA/150)
Device Model:     Maxtor 6L200M0
Firmware Version: BANC1E00
User Capacity:    203,928,109,056 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
Local Time is:    Mon Sep 10 16:03:42 2007 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Warning! SMART Attribute Thresholds Structure error: invalid SMART checksum.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x80)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		 (1562) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  81) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  3 Spin_Up_Time            0x0027   207   207   063    Pre-fail  Always       -       18457
  4 Start_Stop_Count        0x0032   253   253   000    Old_age   Always       -       348
  5 Reallocated_Sector_Ct   0x0033   253   253   063    Pre-fail  Always       -       2
  6 Read_Channel_Margin     0x0001   253   253   100    Pre-fail  Offline      -       0
  7 Seek_Error_Rate         0x000a   253   252   000    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0027   249   239   187    Pre-fail  Always       -       51048
  9 Power_On_Minutes        0x0032   249   249   000    Old_age   Always       -       486h+06m
 10 Spin_Retry_Count        0x002b   253   252   157    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x002b   253   252   223    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   252   252   000    Old_age   Always       -       771
192 Power-Off_Retract_Count 0x0032   253   253   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   253   253   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0032   030   253   000    Old_age   Always       -       28
195 Hardware_ECC_Recovered  0x000a   253   252   000    Old_age   Always       -       3399
196 Reallocated_Event_Count 0x0008   253   253   000    Old_age   Offline      -       0
197 Current_Pending_Sector  0x0008   253   253   000    Old_age   Offline      -       0
198 Offline_Uncorrectable   0x0008   253   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0008   199   199   000    Old_age   Offline      -       0
200 Multi_Zone_Error_Rate   0x000a   253   252   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x000a   253   252   000    Old_age   Always       -       0
202 TA_Increase_Count       0x000a   253   252   000    Old_age   Always       -       0
203 Run_Out_Cancel          0x000b   253   252   180    Pre-fail  Always       -       0
204 Shock_Count_Write_Opern 0x000a   253   252   000    Old_age   Always       -       0
205 Shock_Rate_Write_Opern  0x000a   253   252   000    Old_age   Always       -       0
207 Spin_High_Current       0x002a   253   252   000    Old_age   Always       -       0
208 Spin_Buzz               0x002a   253   252   000    Old_age   Always       -       0
209 Offline_Seek_Performnce 0x0024   239   239   000    Old_age   Offline      -       172
210 Unknown_Attribute       0x0032   253   252   000    Old_age   Always       -       0
211 Unknown_Attribute       0x0032   253   252   000    Old_age   Always       -       0
212 Unknown_Attribute       0x0032   253   247   000    Old_age   Always       -       0

Warning! SMART ATA Error Log Structure error: invalid SMART checksum.
SMART Error Log Version: 1
ATA Error Count: 2
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2 occurred at disk power-on lifetime: 1445 hours (60 days + 5 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 00 00 00 00 00 a0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 00      18:11:16.222  IDENTIFY DEVICE
  25 00 00 61 45 21 e0 00      18:11:10.072  READ DMA EXT
  25 00 80 e1 43 21 e0 00      18:11:10.069  READ DMA EXT
  25 00 88 59 42 21 e0 00      18:11:10.066  READ DMA EXT
  25 00 00 59 40 21 e0 00      18:11:10.062  READ DMA EXT

Error 1 occurred at disk power-on lifetime: 1074 hours (44 days + 18 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  00 00 08 95 54 53 a0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 08 95 54 53 a0 00      00:00:40.081  IDENTIFY DEVICE
  c8 00 08 94 54 53 e1 00      00:00:33.998  READ DMA
  c8 00 08 8c 54 53 e1 00      00:00:33.998  READ DMA
  c8 00 08 84 54 53 e1 00      00:00:33.998  READ DMA
  c8 00 08 7c 54 53 e1 00      00:00:33.998  READ DMA

Error 0 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  00 00 00 00 00 00 00  

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 3b 00 00 00 00 00 00      00:00:00.000  NOP [Reserved subcommand]

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Re: Maxtor 6L200M0 sata irq timeouts

[Tejun Heo]

Michal Suchanek wrote:
>> What does 'smartctl -a /dev/sda' say?
>>
> Attaching output.

Hmmm... How often does the condition occur?  smartlog records only two
occasions.

-- 
tejun

Re: Maxtor 6L200M0 sata irq timeouts

[Michal Suchanek]

Hello

(please CC me when replying)

On 11/09/2007, Tejun Heo <htejun@gmail.com> wrote:
> Michal Suchanek wrote:
> >> What does 'smartctl -a /dev/sda' say?
> >>
> > Attaching output.
>
> Hmmm... How often does the condition occur?  smartlog records only two
> occasions.
>

Every few minutes when the system is under load, less often when not.

I think the logged drive errors are unrelated, the drive delivers the
interrupt, just a bit later than Linux expects. At least that is my
impression after looking at the these logs and the logs from the old
system (I am not sure I could still find the saved logs but with some
combination of irq related kernel options I got spurious interrupt
instead of timeout, and the drive got disabled).

Thanks

Michal

Re: Maxtor 6L200M0 sata irq timeouts

[Tejun Heo]

Michal Suchanek wrote:
> Hello
> 
> (please CC me when replying)
> 
> On 11/09/2007, Tejun Heo <htejun@gmail.com> wrote:
>> Michal Suchanek wrote:
>>>> What does 'smartctl -a /dev/sda' say?
>>>>
>>> Attaching output.
>> Hmmm... How often does the condition occur?  smartlog records only two
>> occasions.
>>
> 
> Every few minutes when the system is under load, less often when not.
> 
> I think the logged drive errors are unrelated, the drive delivers the
> interrupt, just a bit later than Linux expects. At least that is my
> impression after looking at the these logs and the logs from the old
> system (I am not sure I could still find the saved logs but with some
> combination of irq related kernel options I got spurious interrupt
> instead of timeout, and the drive got disabled).

Can you please test the latest rc kernel and see whether this problem is
still there?

Thanks.

-- 
tejun

Re: Maxtor 6L200M0 sata irq timeouts

[Michal Suchanek]

Hello

(please CC me when replying)

On 27/09/2007, Tejun Heo <htejun@gmail.com> wrote:
> Michal Suchanek wrote:
> > On 11/09/2007, Tejun Heo <htejun@gmail.com> wrote:
> >> Michal Suchanek wrote:
> >>>> What does 'smartctl -a /dev/sda' say?
> >>>>
> >>> Attaching output.
> >> Hmmm... How often does the condition occur?  smartlog records only two
> >> occasions.
> >>
> >
> > Every few minutes when the system is under load, less often when not.
> >
> > I think the logged drive errors are unrelated, the drive delivers the
> > interrupt, just a bit later than Linux expects. At least that is my
> > impression after looking at the these logs and the logs from the old
> > system (I am not sure I could still find the saved logs but with some
> > combination of irq related kernel options I got spurious interrupt
> > instead of timeout, and the drive got disabled).
>
> Can you please test the latest rc kernel and see whether this problem is
> still there?
>

With  2.6.23-rc8 I can still reproduce the problem.

I have moved the system to a pata drive and I am going to try and
replace the drive to get rid of both this interrupt stuff and
overheating.

Thanks

Michal

Re: Maxtor 6L200M0 sata irq timeouts

[Michal Suchanek]

On 01/10/2007, Michal Suchanek <hramrach@centrum.cz> wrote:
> Hello
>
> (please CC me when replying)
>
>

I got a replacement drive which is also a 6L200M0 but the fw rev is
now BACE1G10.

Both the irq errors and the smart checksum errors are gone. I guess
these were cause by old and buggy drive firmware in my case.

Thanks

Michal