linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul Check" <paul@thechecks.ca>
To: linux-ide@vger.kernel.org
Subject: Re: Intermittent SATA link down SStatus 0
Date: Thu, 21 Jan 2010 14:24:35 -0500	[thread overview]
Message-ID: <fbae475f602d8f79f27d2d36be0de4f7.squirrel@thechecks.ca> (raw)
In-Reply-To: <f4d0374cb498479438e76ac749465a7d.squirrel@thechecks.ca>

I decided to try running 2.6.31 without the pata_marvell anyway, just to
see what would happen. It will be difficult to diagnose due to the fact
that the problem was only intermittent, but here are some interesting
observations so far:

With my old 2.6.31 kernel and pata_marvell selected, I had been getting
line such as the following in kern.log:

kernel: [    1.293997] scsi0 : pata_marvell
kernel: [    1.294093] scsi1 : pata_marvell

Sometimes instead of scsi0 and scsi1 it would say scsi4 and scsi5.  It
appears that when pata_marvell was associated with scsi0 and scsi1, my
drives would register on ata3 and ata4.  But, when pata_marvell was
associated with scsi4 and scsi5, the drives would be associated with ata1
and ata2.  [Note: The four hard drives are plugged into sata ports 1
through 4, the Sony BWU into port 5 and the front eSATA into port 6.]

Now, with pata_marvell NOT compiled into the kernel, on the first try I am
getting the hard drives on ata1.00, ata1.01, ata2.00 and ata2.01, and the
Sony BWU on sata3, which seems "correct" given the ports I have the drives
plugged into.

Also, I now see:

ata7: DUMMY

whereas before this entry did not occur.

So, it does appear that the pata_marvell module was at least responsible
for the shifting ata entries (answering one of my questions). We'll see if
it also gets rid of the much more serious link down problem.  I will try
multiple reboots later to see if I can trigger that old bad link down
behaviour.

P

> 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:
>
> As I look through kern.log I see that the numbering on the ATA channels is
> not always consistent.  For example, sometimes the Seagates come on
> ata3.00, ata3.01, ata4.00 and ata4.01. Is this usual, or indicating a
> problem with the controller/driver?
>
> Regards, Paul (on list)
>
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



  parent reply	other threads:[~2010-01-21 19:24 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
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 [this message]
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=fbae475f602d8f79f27d2d36be0de4f7.squirrel@thechecks.ca \
    --to=paul@thechecks.ca \
    --cc=linux-ide@vger.kernel.org \
    /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).