From nobody@FreeBSD.org  Tue Jun  8 22:51:23 2010
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E2B4B1065675
	for <freebsd-gnats-submit@FreeBSD.org>; Tue,  8 Jun 2010 22:51:23 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id D1D2F8FC0C
	for <freebsd-gnats-submit@FreeBSD.org>; Tue,  8 Jun 2010 22:51:23 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o58MpNkp097907
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 8 Jun 2010 22:51:23 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id o58MpNq8097906;
	Tue, 8 Jun 2010 22:51:23 GMT
	(envelope-from nobody)
Message-Id: <201006082251.o58MpNq8097906@www.freebsd.org>
Date: Tue, 8 Jun 2010 22:51:23 GMT
From: Volodymyr Kostyrko <c.kworr@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: sys/dev/mpt: new chip revision, partially unsupported
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         147704
>Category:       kern
>Synopsis:       [mpt] sys/dev/mpt: new chip revision, partially unsupported
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-scsi
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jun 08 23:00:14 UTC 2010
>Closed-Date:    Mon Apr 29 06:17:32 UTC 2013
>Last-Modified:  Mon Apr 29 06:17:32 UTC 2013
>Originator:     Volodymyr Kostyrko
>Release:        RELENG_8
>Organization:
>Environment:
FreeBSD flashk0 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0: Sat Jun  5 07:53:25 UTC 2010     arcade@flashk0:/usr/obj/usr/src/sys/MINIMAL_8  amd64

>Description:
When trying to setup system on Supermicro X8DT3 board I found that mpt driver behaves incorrectly. It detects all physical devices and none virtual.

Attaching device gives this:

Jun  8 22:19:33 flashk0 kernel: mpt0: <LSILogic SAS/SATA Adapter> port 0xd000-0xd0ff mem 0xfabec000-0xfabeffff,0xfabf0000-0xfabfffff irq 16 at device 0.0 on pci3
Jun  8 22:19:33 flashk0 kernel: mpt0: [ITHREAD]
Jun  8 22:19:33 flashk0 kernel: mpt0: MPI Version=1.5.18.0
Jun  8 22:19:37 flashk0 kernel: da0 at mpt0 bus 0 scbus0 target 0 lun 0
Jun  8 22:19:37 flashk0 kernel: da0: <HITACHI HUS156030VLS600 A392> Fixed Direct Access SCSI-6 device 
Jun  8 22:19:37 flashk0 kernel: da0: 300.000MB/s transfers
Jun  8 22:19:37 flashk0 kernel: da0: Command Queueing enabled
Jun  8 22:19:37 flashk0 kernel: da0: 286168MB (586072368 512 byte sectors: 255H 63S/T 36481C)
Jun  8 22:19:37 flashk0 kernel: da1 at mpt0 bus 0 scbus0 target 1 lun 0
Jun  8 22:19:37 flashk0 kernel: da1: <HITACHI HUS156030VLS600 A392> Fixed Direct Access SCSI-6 device 
Jun  8 22:19:37 flashk0 kernel: da1: 300.000MB/s transfers
Jun  8 22:19:37 flashk0 kernel: da1: Command Queueing enabled
Jun  8 22:19:37 flashk0 kernel: da1: 286168MB (586072368 512 byte sectors: 255H 63S/T 36481C)
Jun  8 22:19:37 flashk0 kernel: da2 at mpt0 bus 0 scbus0 target 2 lun 0
Jun  8 22:19:37 flashk0 kernel: da2: <HITACHI HUS154545VLS300 A500> Fixed Direct Access SCSI-5 device 
Jun  8 22:19:37 flashk0 kernel: da2: 300.000MB/s transfers
Jun  8 22:19:37 flashk0 kernel: da2: Command Queueing enabled
Jun  8 22:19:37 flashk0 kernel: da2: 429247MB (879097968 512 byte sectors: 255H 63S/T 54721C)
Jun  8 22:19:37 flashk0 kernel: da3 at mpt0 bus 0 scbus0 target 3 lun 0
Jun  8 22:19:37 flashk0 kernel: da3: <HITACHI HUS154545VLS300 A500> Fixed Direct Access SCSI-5 device 
Jun  8 22:19:37 flashk0 kernel: da3: 300.000MB/s transfers
Jun  8 22:19:37 flashk0 kernel: da3: Command Queueing enabled
Jun  8 22:19:37 flashk0 kernel: da3: 429247MB (879097968 512 byte sectors: 255H 63S/T 54721C)
Jun  8 22:19:37 flashk0 kernel: da4 at mpt0 bus 0 scbus0 target 4 lun 0
Jun  8 22:19:37 flashk0 kernel: da4: <ATA WDC WD1002FBYS-0 0C06> Fixed Direct Access SCSI-5 device 
Jun  8 22:19:37 flashk0 kernel: da4: 300.000MB/s transfers
Jun  8 22:19:37 flashk0 kernel: da4: Command Queueing enabled
Jun  8 22:19:37 flashk0 kernel: da4: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
Jun  8 22:19:37 flashk0 kernel: da5 at mpt0 bus 0 scbus0 target 5 lun 0
Jun  8 22:19:37 flashk0 kernel: da5: <ATA WDC WD1002FBYS-0 0C06> Fixed Direct Access SCSI-5 device 
Jun  8 22:19:37 flashk0 kernel: da5: 300.000MB/s transfers
Jun  8 22:19:37 flashk0 kernel: da5: Command Queueing enabled
Jun  8 22:19:37 flashk0 kernel: da5: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
Jun  8 22:19:37 flashk0 kernel: (da4:mpt0:0:4:0): READ(6). CDB: 8 0 0 80 10 0 
Jun  8 22:19:37 flashk0 kernel: (da4:mpt0:0:4:0): CAM status: SCSI Status Error
Jun  8 22:19:37 flashk0 kernel: (da4:mpt0:0:4:0): SCSI status: Check Condition
Jun  8 22:19:37 flashk0 kernel: (da4:mpt0:0:4:0): SCSI sense: ABORTED COMMAND asc:0,0 (No additional sense information)
Jun  8 22:19:40 flashk0 kernel: (da4:mpt0:0:4:0): READ(6). CDB: 8 0 0 80 10 0 
Jun  8 22:19:40 flashk0 kernel: (da4:mpt0:0:4:0): CAM status: SCSI Status Error
Jun  8 22:19:40 flashk0 kernel: (da4:mpt0:0:4:0): SCSI status: Check Condition
Jun  8 22:19:40 flashk0 kernel: (da4:mpt0:0:4:0): SCSI sense: ABORTED COMMAND asc:0,0 (No additional sense information)
Jun  8 22:19:43 flashk0 kernel: (da4:mpt0:0:4:0): READ(6). CDB: 8 0 0 80 10 0 
Jun  8 22:19:43 flashk0 kernel: (da4:mpt0:0:4:0): CAM status: SCSI Status Error
Jun  8 22:19:43 flashk0 kernel: (da4:mpt0:0:4:0): SCSI status: Check Condition
Jun  8 22:19:43 flashk0 kernel: (da4:mpt0:0:4:0): SCSI sense: MEDIUM ERROR info:80 asc:11,0 (Unrecovered read error)
Jun  8 22:19:46 flashk0 kernel: (da4:mpt0:0:4:0): READ(6). CDB: 8 0 0 80 10 0 
Jun  8 22:19:46 flashk0 kernel: (da4:mpt0:0:4:0): CAM status: SCSI Status Error
Jun  8 22:19:46 flashk0 kernel: (da4:mpt0:0:4:0): SCSI status: Check Condition
Jun  8 22:19:46 flashk0 kernel: (da4:mpt0:0:4:0): SCSI sense: ABORTED COMMAND asc:0,0 (No additional sense information)
Jun  8 22:19:50 flashk0 kernel: (da4:mpt0:0:4:0): READ(6). CDB: 8 0 0 80 10 0 
Jun  8 22:19:50 flashk0 kernel: (da4:mpt0:0:4:0): CAM status: SCSI Status Error
Jun  8 22:19:50 flashk0 kernel: (da4:mpt0:0:4:0): SCSI status: Check Condition
Jun  8 22:19:50 flashk0 kernel: (da4:mpt0:0:4:0): SCSI sense: ABORTED COMMAND asc:0,0 (No additional sense information)
Jun  8 22:19:53 flashk0 kernel: (da4:mpt0:0:4:0): READ(6). CDB: 8 0 0 0 10 0 
Jun  8 22:19:53 flashk0 kernel: (da4:mpt0:0:4:0): CAM status: SCSI Status Error
Jun  8 22:19:53 flashk0 kernel: (da4:mpt0:0:4:0): SCSI status: Check Condition
Jun  8 22:19:53 flashk0 kernel: (da4:mpt0:0:4:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)

da4 and da5 currently are in personal RAID0 containers.

pciconf -lv:
mpt0@pci0:3:0:0:        class=0x010000 card=0x000115d9 chip=0x00591000 rev=0x08 hdr=0x00
    vendor     = 'LSI Logic (Was: Symbios Logic, NCR)'
    class      = mass storage
    subclass   = SCSI

# mptutil show adapter
mpt0 Adapter:
       Board Name: UNUSED
   Board Assembly: 
        Chip Name: C1068E
    Chip Revision: UNUSED
      RAID Levels: none

# mptutil show config
mpt0 Configuration: 0 volumes, 6 drives
    drive da0 (279G) ONLINE <HITACHI HUS156030VLS600 A392> SCSI-6
    drive da1 (279G) ONLINE <HITACHI HUS156030VLS600 A392> SCSI-6
    drive da2 (419G) ONLINE <HITACHI HUS154545VLS300 A500> SAS
    drive da3 (419G) ONLINE <HITACHI HUS154545VLS300 A500> SAS
    drive da4 (932G) ONLINE <WDC WD1002FBYS-0 0C06> SATA
    drive da5 (932G) ONLINE <WDC WD1002FBYS-0 0C06> SATA

As I told before I have created two virtual devices on da4 and da5.

# mptutil show events
mptutil: Reading extended config page header failed: Invalid configuration action
mptutil: Failed to get event log info: Input/output error

# mptutil show volumes
mpt0 Volumes:
  Id     Size    Level   Stripe State Write-Cache  Name
>How-To-Repeat:
Simple loading of driver does the job.
>Fix:
None. I've already tried hand-patching the driver (adding code 59) but that doesn't work.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Wed Jun 9 00:16:17 UTC 2010 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=147704 

From: Volodymyr Kostyrko <c.kworr@gmail.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/147704: [mpt] sys/dev/mpt: new chip revision, partially
 unsupported
Date: Wed, 28 Jul 2010 13:40:31 +0300

 Sorry, I was wrong. It's not about mpt driver, it's about firmware.
 
 This RAID controller may be flashed with three distinct firmwares:
 
 1. IR. Integrated RAID. Needs I-Button chip to work.
 2. SR. Software RAID. Unsupported on FreeBSD.
 3. IT. Integrated Target. Shows connected device only.
 
 I've contacted SuperMicro and obtained firmware to flash my controller 
 from SR mode to IT mode and now it works.
 
 Maybe it's just worth mentioning on mpt(4) about different firmwares 
 available?
 
 -- 
 Sphinx of black quartz judge my vow.
State-Changed-From-To: open->closed 
State-Changed-By: sbruno 
State-Changed-When: Mon Apr 29 06:17:02 UTC 2013 
State-Changed-Why:  
User reported that this was fixed by firmware updates. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=147704 
>Unformatted:
