Re: Frequent SATA resets with sata_nv (fwd)

Re: Frequent SATA resets with sata_nv (fwd)

[Robert Hancock]

(ccing linux-ide)

Matthew "Cheetah" Gabeler-Lee wrote:
> (Please cc me on replies)
> 
> I have three samsung hdds (/sys/block/sda/device/model says SAMSUNG 
> SP2504C) in a raid configuration.  My system frequently (2-3x/day) 
> experiences temporary lockups, which produce messages as below in my 
> dmesg/syslog.  The system recovers, but the hang is annoying to say the 
> least.
> 
> All three drives are connected to sata_nv ports.  Oddly, it almost 
> always happens on ata6 or ata7 (the second and third ports of that 4 
> port setup on my motherboard).  There is an identical drive connected at 
> ata5, but I've only once or twice seen it hit that drive.
> 
> Googling around lkml.org, I found a few threads investigating what look 
> like very similar problems, some of which never seemed to find the 
> solution, but one of which came up with a fairly quick answer it seemed, 
> namely that the drive's NCQ implementation was horked: 
> http://lkml.org/lkml/2007/4/18/32
> 
> While I don't have older logs to verify exactly when this started, it 
> was fairly recent, perhaps around my 2.6.20.1 to 2.6.21.1 kernel 
> upgrade.
> 
> Any other info or tests I can provide/run to help?
> 
> Syslog snippet:
> Jun 21 10:35:23 cheetah kernel: ata6: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x0 next cpb idx 0x0
> Jun 21 10:35:24 cheetah kernel: ata6: CPB 0: ctl_flags 0x9, resp_flags 0x0
> Jun 21 10:35:24 cheetah kernel: ata6: timeout waiting for ADMA IDLE, stat=0x400
> Jun 21 10:35:24 cheetah kernel: ata6: timeout waiting for ADMA LEGACY, stat=0x400
> Jun 21 10:35:24 cheetah kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jun 21 10:35:24 cheetah kernel: ata6.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0
> Jun 21 10:35:24 cheetah kernel:          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jun 21 10:35:24 cheetah kernel: ata6: soft resetting port
> Jun 21 10:35:24 cheetah kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> Jun 21 10:35:24 cheetah kernel: ata6.00: configured for UDMA/133
> Jun 21 10:35:24 cheetah kernel: ata6: EH complete
> Jun 21 10:35:24 cheetah kernel: SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
> Jun 21 10:35:24 cheetah kernel: sdb: Write Protect is off
> Jun 21 10:35:24 cheetah kernel: sdb: Mode Sense: 00 3a 00 00
> Jun 21 10:35:24 cheetah kernel: SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Unfortunately, this kind of problem is rather difficult to diagnose. 
Essentially what's happened is that we've sent a command (in this case a 
cache flush) to the controller but it's given no indication that it's 
done anything with it (somewhat different from the case in the link you 
mentioned above, where the controller indicates it's sent the command 
and is waiting for completion). This could be some kind of drive issue 
or drive/controller incompatibility, a controller bug, the driver doing 
something the controller doesn't expect..

Does this drive actually support NCQ? I can't tell from this part of the 
  log.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

Re: Frequent SATA resets with sata_nv (fwd)

[Matthew "Cheetah" Gabeler-Lee]

On Sun, 24 Jun 2007, Robert Hancock wrote:

> Matthew "Cheetah" Gabeler-Lee wrote:
> > (Please cc me on replies)
> > 
> > I have three samsung hdds (/sys/block/sda/device/model says SAMSUNG SP2504C)
> > in a raid configuration.  My system frequently (2-3x/day) experiences
> > temporary lockups, which produce messages as below in my dmesg/syslog.  The
> > system recovers, but the hang is annoying to say the least.
> 
> Does this drive actually support NCQ? I can't tell from this part of the  log.

I selected that model in part because it at least claimed to support 
NCQ.  I'm not sure if it reflects NCQ or not, but I do have 
/sys/block/sd[abc]/device/queue_{depth,type} which show simple and 31 
respectively.  Samsung's page for the drive also says it supports NCQ: 
http://www.samsung.com/Products/HardDiskDrive/SpinPointPSeries/HardDiskDrive_SpinPointPSeries_SP2504C.htm

-- 
	-Cheetah
"Reality is that which, when you stop believing in it, doesn't go away".
                -- Philip K. Dick
GPG pubkey fingerprint: A57F B354 FD30 A502 795B 9637 3EF1 3F22 A85E 2AD1

Re: Frequent SATA resets with sata_nv (fwd)

[Heinz Ulrich Stille]

On Tuesday 26 June 2007, Matthew "Cheetah" Gabeler-Lee wrote:
> On Sun, 24 Jun 2007, Robert Hancock wrote:
> I selected that model in part because it at least claimed to support
> NCQ.  I'm not sure if it reflects NCQ or not, but I do have
> /sys/block/sd[abc]/device/queue_{depth,type} which show simple and 31
> respectively.  Samsung's page for the drive also says it supports NCQ:

I seem to have the same problem, just not as frequent: four drives of this
type, connected to an SiI 3132 and an nVidia MCP55; resets occur on both
controllers, and only with this drive type, not with several Maxtor 6B200M0.
I never thought to check, but all drives on the nv controller have NCQ
disabled according to /sys/block. So maybe it's not (directly) NCQ related?

MfG, Ulrich

-- 
Heinz Ulrich Stille / Tel.: +49-541-9400473 / Fax: +49-541-9400450
design_d gmbh / Wilhelmstr. 16 / 49076 Osnabrück / www.design-d.de
Osnabrück HRB 19116 / Geschäftsführer: Günter Tammen, Rolf Tammen