From: "Hajo Möller" <dasjoe@gmail.com>
To: linux-scsi@vger.kernel.org
Cc: yuxiangl@marvell.com
Subject: Can not see/access devices on Marvell 88SE9485 + SiI 3726 PMP
Date: Mon, 01 Jul 2013 16:09:42 +0200 [thread overview]
Message-ID: <51D18DA6.8000502@gmail.com> (raw)
Hi,
I've got a box which recently got a Marvell 88SE9485 PCIe card
(Supermicro AOC-SAS2LP-MV8), which is connected by a mSAS->4x SATA-cable
to some 5 HDD backplanes (CFI-B53PM, chip is a SiI 3726).
The HBA's BIOS can see and access the HDDs through the backplanes, which
various Linux distributions could not.
I tried Ubuntu 12.04.2, Ubuntu 13.04, Debian 7.0 and a current Arch Linux.
All logs in this mail are from a fresh Ubuntu 12.04.2 install.
lspci shows the controller as:
01:00.0 RAID bus controller: Marvell Technology Group Ltd. Device 9485
(rev 03)
lshw does not show the attached disks, nor are there device nodes in
/dev/ for those disks.
Unplugging a disk results in this (/var/log/kern.log):
kernel: [ 276.995910]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2062:phy 4 ctrl sts=0x00000000.
kernel: [ 276.995914]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2064:phy 4 irq sts = 0x01201001
kernel: [ 278.950547]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2062:phy 4 ctrl sts=0x00111000.
kernel: [ 278.950551]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2064:phy 4 irq sts = 0x00000081
kernel: [ 279.502757]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_94xx.c
838:get all reg link rate is 0x111000
kernel: [ 279.502760]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_94xx.c
843:get link rate is 9
kernel: [ 279.582118] mvsas 0000:01:00.0: Phy0 : No sig fis
kernel: [ 279.582121]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2006:phy0 Attached Device
kernel: [ 283.953502]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2048:Get signature time out, reset phy 4
kernel: [ 283.953517]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2062:phy 4 ctrl sts=0x00000000.
kernel: [ 283.953519]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2064:phy 4 irq sts = 0x00001001
kernel: [ 284.449485]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2062:phy 4 ctrl sts=0x00111000.
kernel: [ 284.449488]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2064:phy 4 irq sts = 0x00000081
kernel: [ 286.445635]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_94xx.c
838:get all reg link rate is 0x111000
kernel: [ 286.445638]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_94xx.c
843:get link rate is 9
kernel: [ 286.524997] mvsas 0000:01:00.0: Phy0 : No sig fis
kernel: [ 286.525000]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2006:phy0 Attached Device
Replugging the disk:
kernel: [ 310.738784]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2062:phy 4 ctrl sts=0x00111000.
kernel: [ 310.738788]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2064:phy 4 irq sts = 0x00010000
kernel: [ 310.738791]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
2113:notify plug in on phy[0]
kernel: [ 310.758632]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_94xx.c
838:get all reg link rate is 0x111000
kernel: [ 310.758634]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_94xx.c
843:get link rate is 9
kernel: [ 310.877669]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
1175:phy 4 attach dev info is 20001
kernel: [ 310.877671]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
1177:phy 4 attach sas addr is 4
kernel: [ 310.877678]
/build/buildd/linux-lts-quantal-3.5.0/drivers/scsi/mvsas/mv_sas.c
277:phy 4 byte dmaded.
kernel: [ 310.877689] sas: sas_form_port: phy0 belongs to port0 already(1)!
According to Marvell's product brief the controller has "Built-in
support for SATA Port Multipliers with FIS-based switching", which its
BIOS seems to confirm.
The PMPs used to work when connected via a Syba SY-PEX40008 (SiI3124)
controller, which has bugs on its own when more than three drives per
PMP are concurrently active.
Any help is greatly appreciated,
Hajo
next reply other threads:[~2013-07-01 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 14:09 Hajo Möller [this message]
2013-07-01 14:38 ` Can not see/access devices on Marvell 88SE9485 + SiI 3726 PMP James Bottomley
2013-07-03 12:52 ` Hajo Möller
2013-07-03 15:07 ` James Bottomley
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=51D18DA6.8000502@gmail.com \
--to=dasjoe@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=yuxiangl@marvell.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).