Re: Adaptec 1405 and mvsas

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

following up to my earlier mail from September 4th.

Marco Gruß wrote:
> I recently acquired an Adaptec 1405 SAS/SATA HBA.
> 
> While there is a closed-source driver by Adaptec, called adpinv, I'd of
> course like to get it to work with open drivers.
> 
> A lspci -v reveals that the controller is actually using a Marvell chip:
> 
> 02:00.0 Serial Attached SCSI controller: Adaptec Device 0450 (rev 02)
>         Subsystem: Marvell Technology Group Ltd. Device 6440
> 
> 02:00.0 0107: 9005:0450 (rev 02)
>         Subsystem: 11ab:6440
> 
> (The output of lspci -vv is attached below)
> 
> So I simply added an entry for this PCI id to mvsas.c:
> 
> [...]
> 
> ...with limited success:

I noticed that the mvsas driver seems to have changed quite a lot
in 2.6.31, since there's now a subdir for it. I figured I'd try
my simple PCI ID hack again:

--- /usr/src/linux-2.6.31/drivers/scsi/mvsas/mv_init.c  2009-09-19
23:09:44.000000000 +0200
+++ /usr/src/linux-2.6.31/drivers/scsi/mvsas/mv_init.c.orig     2009-09-10
00:13:59.000000000 +0200
@@ -653,15 +653,6 @@
         { PCI_VDEVICE(MARVELL, 0x6485), chip_6485 },
         { PCI_VDEVICE(MARVELL, 0x9480), chip_9480 },
         { PCI_VDEVICE(MARVELL, 0x9180), chip_9180 },
-       {
-               .vendor         = PCI_VENDOR_ID_ADAPTEC2,
-               .device         = 0x0450,
-               .subvendor      = PCI_VENDOR_ID_MARVELL,
-               .subdevice      = 0x6440,
-               .class          = 0,
-               .class_mask     = 0,
-               .driver_data    = chip_6440,
-       },

         { }     /* terminate list */
  };


This time I get the following upon loading (on x86_64):

Sep 19 23:24:42 debian kernel: mvsas 0000:02:00.0: mvsas: driver version
0.8.2
Sep 19 23:24:42 debian kernel: mvsas 0000:02:00.0: PCI INT A -> GSI 19
(level, low) -> IRQ 19
Sep 19 23:24:42 debian kernel: mvsas 0000:02:00.0: setting latency timer to
64
Sep 19 23:24:42 debian kernel: mvsas 0000:02:00.0: mvsas: PCI-E x4,
Bandwidth Usage: 2.5 Gbps
Sep 19 23:24:44 debian kernel: drivers/scsi/mvsas/mv_sas.c 1214:port 0
attach dev info is 0
Sep 19 23:24:44 debian kernel: drivers/scsi/mvsas/mv_sas.c 1216:port 0
attach sas addr is 0
Sep 19 23:24:44 debian kernel: drivers/scsi/mvsas/mv_sas.c 1214:port 1
attach dev info is 0
Sep 19 23:24:44 debian kernel: drivers/scsi/mvsas/mv_sas.c 1216:port 1
attach sas addr is 0
Sep 19 23:24:44 debian kernel: drivers/scsi/mvsas/mv_sas.c 1214:port 2
attach dev info is 20000
Sep 19 23:24:44 debian kernel: drivers/scsi/mvsas/mv_sas.c 1216:port 2
attach sas addr is 2
Sep 19 23:24:45 debian kernel: drivers/scsi/mvsas/mv_sas.c 1214:port 3
attach dev info is 40400
Sep 19 23:24:45 debian kernel: drivers/scsi/mvsas/mv_sas.c 1216:port 3
attach sas addr is 3
Sep 19 23:24:45 debian kernel: scsi5 : mvsas
Sep 19 23:24:45 debian kernel: drivers/scsi/mvsas/mv_sas.c 380:phy 2 byte
dmaded.
Sep 19 23:24:45 debian kernel: drivers/scsi/mvsas/mv_sas.c 380:phy 3 byte
dmaded.
Sep 19 23:24:45 debian kernel: sas: phy-5:2 added to port-5:0, phy_mask:0x4
( 200000000000000)
Sep 19 23:24:45 debian kernel: sas: phy-5:3 added to port-5:1, phy_mask:0x8
( 300000000000000)
Sep 19 23:24:45 debian kernel: sas: DOING DISCOVERY on port 0, pid:2236
Sep 19 23:24:45 debian kernel: drivers/scsi/mvsas/mv_sas.c 1365:found
dev[0:5] is gone.
Sep 19 23:24:45 debian kernel: sas: sas_ata_phy_reset: Found ATA device.
Sep 19 23:24:45 debian kernel: ata7.00: ATA-7: OCZ-VERTEX, 1.3, max UDMA/133
Sep 19 23:24:45 debian kernel: ata7.00: 62533296 sectors, multi 1: LBA48 NCQ
(depth 31/32)
Sep 19 23:24:45 debian kernel: ata7.00: configured for UDMA/133
Sep 19 23:24:45 debian kernel: scsi 5:0:0:0: Direct-Access     ATA
OCZ-VERTEX       1.3  PQ: 0 ANSI: 5
Sep 19 23:24:45 debian kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
Sep 19 23:24:45 debian kernel: sas: DONE DISCOVERY on port 0, pid:2236,
result:0
Sep 19 23:24:45 debian kernel: sas: DOING DISCOVERY on port 1, pid:2236
Sep 19 23:24:45 debian kernel: sd 5:0:0:0: [sdd] 62533296 512-byte logical
blocks: (32.0 GB/29.8 GiB)
Sep 19 23:24:45 debian kernel: sd 5:0:0:0: [sdd] Write Protect is off
Sep 19 23:24:45 debian kernel: sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Sep 19 23:24:45 debian kernel: sd 5:0:0:0: [sdd] Write cache: enabled, read
cache: enabled, doesn't support DPO or FUA
Sep 19 23:24:45 debian kernel:  sdd: sdd1 sdd2
Sep 19 23:24:45 debian kernel: sd 5:0:0:0: [sdd] Attached SCSI disk
Sep 19 23:24:45 debian kernel: drivers/scsi/mvsas/mv_sas.c 1365:found
dev[1:5] is gone.
Sep 19 23:24:45 debian kernel: sas: sas_ata_phy_reset: Found ATAPI device.
Sep 19 23:24:45 debian kernel: ata8.00: ATAPI: HL-DT-ST DVDRAM GH20NS15,
IL00, max UDMA/100
Sep 19 23:24:45 debian kernel: ata8.00: configured for UDMA/100
Sep 19 23:24:45 debian kernel: scsi 5:0:1:0: CD-ROM            HL-DT-ST
DVDRAM GH20NS15  IL00 PQ: 0 ANSI: 5
Sep 19 23:24:45 debian kernel: sr0: scsi3-mmc drive: 48x/48x writer dvd-ram
cd/rw xa/form2 cdda tray
Sep 19 23:24:45 debian kernel: sr 5:0:1:0: Attached scsi CD-ROM sr0
Sep 19 23:24:45 debian kernel: sr 5:0:1:0: Attached scsi generic sg4 type 5
Sep 19 23:24:45 debian kernel: sas: DONE DISCOVERY on port 1, pid:2236,
result:0

This looks much better; the performance isn't exactly stellar though.

Doing 'sync; time (dd if=/dev/zero of=1G bs=1024 count=1024k; sync)'
on the SSD shows me about 40MB/s are written to disk. The same SSD
achieves 150MB/s on an Intel ICH10.

Also, during this experiment, I get some of these in the syslog:

Sep 19 23:25:26 debian kernel: drivers/scsi/mvsas/mv_sas.c 2023:port 2 ctrl
sts=0x199800.
Sep 19 23:25:26 debian kernel: drivers/scsi/mvsas/mv_sas.c 2025:Port 2 irq
sts = 0x1000000
Sep 19 23:25:28 debian kernel: drivers/scsi/mvsas/mv_sas.c 2023:port 2 ctrl
sts=0x199800.
Sep 19 23:25:28 debian kernel: drivers/scsi/mvsas/mv_sas.c 2025:Port 2 irq
sts = 0x1000000
Sep 19 23:25:30 debian kernel: drivers/scsi/mvsas/mv_sas.c 2023:port 2 ctrl
sts=0x199800.
Sep 19 23:25:30 debian kernel: drivers/scsi/mvsas/mv_sas.c 2025:Port 2 irq
sts = 0x1000000

As stated in my previous mail: Anything I can to do help get
this controller working nicely, I'll do ;-)

Thanks!

Marco

CC-ing Marvell persons 
Jack


--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux