From owner-freebsd-i386@FreeBSD.ORG Sat May 22 08:10:27 2004 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E92D716A4CE for ; Sat, 22 May 2004 08:10:27 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD07743D3F for ; Sat, 22 May 2004 08:10:27 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i4MFA6io037052 for ; Sat, 22 May 2004 08:10:06 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i4MFA620037051; Sat, 22 May 2004 08:10:06 -0700 (PDT) (envelope-from gnats) Resent-Date: Sat, 22 May 2004 08:10:06 -0700 (PDT) Resent-Message-Id: <200405221510.i4MFA620037051@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-i386@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, JD Bronson Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCD6D16A4CE for ; Sat, 22 May 2004 08:06:29 -0700 (PDT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0B3743D2D for ; Sat, 22 May 2004 08:06:29 -0700 (PDT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i4MF5bjq034394 for ; Sat, 22 May 2004 08:05:37 -0700 (PDT) (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id i4MF5bIg034393; Sat, 22 May 2004 08:05:37 -0700 (PDT) (envelope-from nobody) Message-Id: <200405221505.i4MF5bIg034393@www.freebsd.org> Date: Sat, 22 May 2004 08:05:37 -0700 (PDT) From: JD Bronson To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: i386/67047: mpt driver does not recognize messages from LSI card X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 May 2004 15:10:28 -0000 >Number: 67047 >Category: i386 >Synopsis: mpt driver does not recognize messages from LSI card >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat May 22 08:10:05 PDT 2004 >Closed-Date: >Last-Modified: >Originator: JD Bronson >Release: 5.2.1 >Organization: Aurora Health Care >Environment: FreeBSD shadow 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Thu May 20 18:55:53 CDT 2004 jbronson@shadow:/usr/src/sys/i386/compile/SHADOW i386 >Description: When RAID is setup on the LSI 20320-R card, and the mirrors start to resync, freebsd is told, but does not understand the error/status message. I am concerned that if a mirror failed, freebsd would not be able to report this as well: mpt0: port 0x5400-0x54ff mem 0xedaa0000-0xedaaffff,0xedab0000-0xedabffff irq 20 at device 3.0 on pci1 .. Timecounters tick every 10.000 msec Waiting 10 seconds for SCSI devices to settle mpt0: Unknown event 0xb mpt0: Unknown event 0xb GEOM: create disk da0 dp=0xc7b72050 .. da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 35000MB (71682030 512 byte sectors: 255H 63S/T 4462C) >How-To-Repeat: >Fix: add support to driver to reflect RAID status/changes - something like this under solaris: May 19 19:40:10 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 19:40:10 shadow Rev. 7 LSI, Inc. 1030 found. May 19 19:40:10 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 19:40:10 shadow mpt0 supports power management. May 19 19:40:23 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 19:40:23 shadow mpt0 Firmware version v1.3.24.0 May 19 19:40:23 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 19:40:23 shadow mpt0: IOC Operational. May 19 19:40:35 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 19:40:35 shadow Volume 0 is optimal May 19 19:40:37 shadow unix: PCI-device: pci1000,1060 at 3, mpt0 May 19 19:40:37 shadow unix: mpt0 is /pci at 1,0/pci1000,1060 at 3 I can tell that the RAID is fine (optimal) and if it is not, I would see this: May 19 16:46:51 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 16:46:51 shadow Rev. 7 LSI, Inc. 1030 found. May 19 16:46:51 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 16:46:51 shadow mpt0 supports power management. May 19 16:47:04 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 16:47:04 shadow mpt0 Firmware version v1.3.24.0 May 19 16:47:04 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 16:47:04 shadow mpt0: IOC Operational. May 19 16:47:16 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 16:47:16 shadow Volume 0 is resyncing May 19 16:47:16 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 16:47:16 shadow Volume 0 is degraded May 19 16:47:18 shadow unix: PCI-device: pci1000,1060 at 3, mpt0 May 19 16:47:18 shadow unix: mpt0 is /pci at 1,0/pci1000,1060 at 3 May 19 16:47:19 shadow unix: /pci at 1,0/pci1000,1060 at 3 (mpt0): May 19 16:47:19 shadow Volume 0 is |enabled||resyncing||degraded| >Release-Note: >Audit-Trail: >Unformatted: