public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <pturmel-kernel@turmel.org>
To: Phil Reynolds <phil-linux@tinsleyviaduct.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Marvell eSATA - 88SE6121 on Asus M3A79-T Deluxe - not in AHCI
Date: Tue, 11 May 2010 14:28:03 -0400	[thread overview]
Message-ID: <4BE9A1B3.3020208@turmel.org> (raw)
In-Reply-To: <20100511182128.216144e4uzjtufbs@topdeck.tinsleyviaduct.com>

On 05/11/2010 01:21 PM, Phil Reynolds wrote:
> Quoting "Phil Turmel" <pturmel-kernel@turmel.org>:
> 
>> I have a similar chipset in my office server: 88SE6145.  If yours can run
>> in AHCI mode, you just need "ahci.marvell_enable=1" on your kernel
>> command
>> line, or "options ahci marvell_enable=1" in your modprobe.conf.  (I have
>> ahci built-in, and no initramfs, so I put the option in my grub.conf.)
> 
> Neither works for me unfortunately.
> 

Hmmm.  If you post your dmesg, lspci, and config, I'll be happy to compare
to my setup.  It might be something as simple as the Marvell driver loading
first and claiming the device.

The relevant part of my dmesg looks like this:

[    4.802703] ahci 0000:06:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    4.806351] ahci 0000:06:00.0: controller can't do NCQ, turning off CAP_NCQ
[    4.809921] ahci 0000:06:00.0: controller can't do PMP, turning off CAP_PMP
[    4.813334] ahci 0000:06:00.0: MV_AHCI HACK: port_map 1f -> f
[    4.816656] ahci 0000:06:00.0: Disabling your PATA port. Use the boot option 'ahci.marvell_enable=0' to avoid this.
[    4.823333] ahci: SSS flag set, parallel bus scan disabled
[    4.826765] ahci 0000:06:00.0: AHCI 0001.0000 32 slots 5 ports 3 Gbps 0xf impl RAID mode
[    4.830240] ahci 0000:06:00.0: flags: 64bit stag slum part
[    4.833810] ahci 0000:06:00.0: setting latency timer to 64
[    4.834021] scsi4 : ahci
[    4.837755] scsi5 : ahci
[    4.841426] scsi6 : ahci
[    4.844997] scsi7 : ahci
[    4.848509] scsi8 : ahci
[    4.851956] ata5: SATA max UDMA/133 irq_stat 0x02400000, PHY RDY changed irq 17
[    4.855423] ata6: SATA max UDMA/133 irq_stat 0x02400000, PHY RDY changed irq 17
[    4.858814] ata7: SATA max UDMA/133 abar m1024@0xfbfffc00 port 0xfbfffe00 irq 17
[    4.862177] ata8: SATA max UDMA/133 abar m1024@0xfbfffc00 port 0xfbfffe80 irq 17
[    4.865472] ata9: DUMMY

The Marvell driver never gets a chance to claim my device, as it is disabled in
my kernel config.  If you are using modules, you might want to blacklist "sata_mv".

If you are using modules from an initramfs, you might need to update your
initramfs, too.

Phil

  reply	other threads:[~2010-05-11 18:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-09 14:13 Marvell eSATA - 88SE6121 on Asus M3A79-T Deluxe - not in AHCI Phil Reynolds
2010-05-11 14:08 ` Phil Turmel
2010-05-11 16:53   ` Phil Reynolds
2010-05-11 17:21   ` Phil Reynolds
2010-05-11 18:28     ` Phil Turmel [this message]
2010-05-11 21:09       ` Jeff Garzik
2010-05-12  2:11         ` Phil Turmel
2010-05-12  6:01           ` Jeff Garzik
2010-05-12  4:59       ` Phil Reynolds
2010-05-11 19:14     ` John Stoffel
2010-05-15 11:18       ` Phil Reynolds

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=4BE9A1B3.3020208@turmel.org \
    --to=pturmel-kernel@turmel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=phil-linux@tinsleyviaduct.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