From: Jeff Garzik <jeff@garzik.org>
To: Paul Check <paul@thechecks.ca>
Cc: linux-ide@vger.kernel.org
Subject: Re: Intermittent SATA link down SStatus 0
Date: Thu, 21 Jan 2010 11:49:16 -0500 [thread overview]
Message-ID: <4B58858C.5080502@garzik.org> (raw)
In-Reply-To: <f4d0374cb498479438e76ac749465a7d.squirrel@thechecks.ca>
On 01/21/2010 10:57 AM, Paul Check wrote:
> I am having an intermittent problem:
>
> ata1.01: SATA link down (SStatus 0 SControl 301)
>
> which is causing one of my four hard drives to not get recognized.
>
> This happens on ata1.01, ata2.00 or ata2.01, although it seems to happen
> more on the 01 channels, I believe. My motherboard is an ASUS P6T Deluxe
> V2, with the Marvel 88SE61XX ATA controller.
>
> I am running the 2.6.31 kernel. A variety of ATA controllers are enabled
> in my kernel (as per default?) including AHCI SATA Support (SATA_AHCI),
> Marvell SATA Support (SATA_MV), Generic ATA Support (ATA_Generic), and
> Marvell PATA Support via Legacy Mode (PATA_MARVELL), among others.
>
> I see that the pata, generic and ahci are getting loaded (from lsmod):
>
> libata 189532 4 pata_marvell,ata_generic,ahci,ata_piix
>
> I am not using hardware RAID (although do have software RAID 1 running).
>
> The BIOS for the board has been updated to the latest version. The disks
> are Seagate ST31000528AS 1 TB drives (4 of them, 2 sets of RAID 1). I
> also have a Sony BWU-300S plugged in.
>
> Would deselecting the pata_marvell likely get rid of this problem? The
> descriptor says:
Link-down means the hardware is reporting that the link between host and
drive disconnected. Removing unused or PATA drivers will probably not
have any effect.
Check your SATA cables and/or power supply.
Jeff
next prev parent reply other threads:[~2010-01-21 16:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 15:57 Intermittent SATA link down SStatus 0 Paul Check
2010-01-21 16:28 ` Paul Check
2010-01-21 16:35 ` Paul Check
2010-01-21 16:49 ` Jeff Garzik [this message]
2010-01-21 16:55 ` Paul Check
2010-01-21 17:11 ` Alan Cox
2010-01-21 17:24 ` Paul Check
2010-01-21 17:36 ` Paul Check
2010-01-21 19:24 ` Paul Check
2010-01-21 21:08 ` Paul Check
2010-01-25 5:06 ` Tejun Heo
2010-02-05 3:29 ` Tim
2010-02-09 5:32 ` Paul Check
2010-07-12 16:32 ` Paul Check
2010-07-12 16:36 ` Paul Check
2010-07-14 12:26 ` Tejun Heo
2010-07-14 17:58 ` Paul Check
2010-07-14 23:36 ` Tejun Heo
2010-07-15 0:43 ` Paul Check
2010-07-15 9:20 ` Tejun Heo
2010-07-15 9:29 ` Tejun Heo
2010-07-15 17:06 ` Paul Check
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=4B58858C.5080502@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=paul@thechecks.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.