linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	linux-ide@vger.kernel.org, xfs@oss.sgi.com,
	Alan Piszcz <ap@solarrain.com>
Subject: Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
Date: Sat, 05 Jul 2008 17:22:16 -0600	[thread overview]
Message-ID: <48700228.7060904@shaw.ca> (raw)
In-Reply-To: <alpine.DEB.1.10.0807051527210.8002@p34.internal.lan>

Justin Piszcz wrote:
>> Can you post your dmesg from bootup with the controller/drive detection?
> 
> Below:
> 
> [    0.889917] ahci 0000:00:1f.2: version 3.0
> [    0.889931] ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 19 (level, 
> low) -> IRQ 19
> [    1.890735] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 6 ports 3 Gbps 
> 0x3f impl SATA mode
> [    1.890845] ahci 0000:00:1f.2: flags: 64bit ncq sntf led clo pio slum 
> part [    1.890940] PCI: Setting latency timer of device 0000:00:1f.2 to 64
> [    1.891185] scsi0 : ahci
> [    1.891310] scsi1 : ahci
> [    1.891419] scsi2 : ahci
> [    1.891527] scsi3 : ahci
> [    1.891806] scsi4 : ahci
> [    1.892805] scsi5 : ahci
> [    1.893844] ata1: SATA max UDMA/133 abar m2048@0xe0625000 port 
> 0xe0625100 irq 378
> [    1.894714] ata2: SATA max UDMA/133 abar m2048@0xe0625000 port 
> 0xe0625180 irq 378
> [    1.895713] ata3: SATA max UDMA/133 abar m2048@0xe0625000 port 
> 0xe0625200 irq 378
> [    1.896713] ata4: SATA max UDMA/133 abar m2048@0xe0625000 port 
> 0xe0625280 irq 378
> [    1.897723] ata5: SATA max UDMA/133 abar m2048@0xe0625000 port 
> 0xe0625300 irq 378
> [    1.898713] ata6: SATA max UDMA/133 abar m2048@0xe0625000 port 
> 0xe0625380 irq 378
> [    2.356649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [    2.673654] ata1.00: ATA-8: WDC WD3000GLFS-01F8U0, 03.03V01, max 
> UDMA/133
> [    2.674595] ata1.00: 586072368 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [    2.679961] ata1.00: configured for UDMA/133
> [    2.836575] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [    3.155395] ata2.00: ATA-8: WDC WD3000GLFS-01F8U0, 03.03V01, max 
> UDMA/133
> [    3.155521] ata2.00: 586072368 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [    3.161112] ata2.00: configured for UDMA/133
> [    3.322501] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [    3.633983] ata3.00: ATA-8: WDC WD3000GLFS-01F8U0, 03.03V01, max 
> UDMA/133
> [    3.634449] ata3.00: 586072368 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [    3.640394] ata3.00: configured for UDMA/133
> [    3.806428] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [    4.112403] ata4.00: ATA-8: WDC WD3000GLFS-01F8U0, 03.03V01, max 
> UDMA/133
> [    4.113376] ata4.00: 586072368 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [    4.119137] ata4.00: configured for UDMA/133
> [    4.397339] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [    4.591563] ata5.00: ATA-8: WDC WD3000GLFS-01F8U0, 03.03V01, max 
> UDMA/133
> [    4.592303] ata5.00: 586072368 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [    4.598246] ata5.00: configured for UDMA/133
> [    4.881265] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [    5.069692] ata6.00: ATA-8: WDC WD3000GLFS-01F8U0, 03.03V01, max 
> UDMA/133
> [    5.070230] ata6.00: 586072368 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [    5.076402] ata6.00: configured for UDMA/133

So you've got 6 drives in the machine. Intel chipsets normally seem 
pretty robust with AHCI.

> [107360.796671] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 
> 0x2 frozen
> [107360.796680] ata4.00: cmd b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
> [107360.796681]          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 
> 0x4 (timeout)
> [107360.796685] ata4.00: status: { DRDY }
> [107361.099615] ata4: soft resetting link
> [107361.252599] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [107361.273562] ata4.00: configured for UDMA/133
> [107361.273604] ata4: EH complete
> [107361.018520] sd 3:0:0:0: [sdd] 586072368 512-byte hardware sectors 
> (300069 MB)
> [107361.018683] sd 3:0:0:0: [sdd] Write Protect is off
> [107361.018687] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
> [107361.040887] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: 
> enabled, doesn't support DPO or FUA

Are you certain that your machine has enough power to run all those 
drives properly? We've seen in a number of cases that power fluctuations 
or noise can cause these kinds of errors.

  reply	other threads:[~2008-07-05 23:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.u8J+BqAcxU1mg8ob9pMBJaAHBPo@ifi.uio.no>
2008-07-05 18:38 ` Lots of con-current I/O = resets SATA link? (2.6.25.10) Robert Hancock
2008-07-05 18:54   ` Jon Nelson
2008-07-05 19:04     ` Robert Hancock
2008-07-05 19:28   ` Justin Piszcz
2008-07-05 23:22     ` Robert Hancock [this message]
2008-07-05 23:24       ` Justin Piszcz
2008-07-06 10:31         ` Justin Piszcz
2008-07-06 12:13           ` Justin Piszcz
2008-07-06 12:42             ` Justin Piszcz
2008-07-06 19:51               ` Justin Piszcz
2008-07-07  9:45         ` Mattias Wadenstein
2008-07-07  9:57           ` Justin Piszcz
2008-07-07 18:14             ` Michal Soltys
2008-07-05 16:57 Justin Piszcz
2008-07-05 17:35 ` Jon Nelson
2008-07-05 17:35 ` Jon Nelson
2008-07-07 15:04 ` Gerhard Wiesinger
2008-07-07 15:08   ` Gerhard Wiesinger
2008-07-07 16:04     ` Justin Piszcz
2008-07-08  6:24       ` Gerhard Wiesinger
2008-07-08  6:59         ` Gerhard Wiesinger
2008-07-08  8:35           ` Justin Piszcz
2008-07-08 10:31             ` Gerhard Wiesinger
2008-07-08  8:34         ` Justin Piszcz
2008-07-08 10:33           ` Gerhard Wiesinger
2008-07-08 13:15             ` Justin Piszcz
2008-07-09  5:37               ` Gerhard Wiesinger
2008-07-10  1:27                 ` Henrique de Moraes Holschuh
2008-07-12  8:29                 ` Gerhard Wiesinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48700228.7060904@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=ap@solarrain.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).