From owner-freebsd-scsi@FreeBSD.ORG Tue Dec 6 07:21:44 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 968E216A41F for ; Tue, 6 Dec 2005 07:21:44 +0000 (GMT) (envelope-from brunomiguel@dequim.ist.utl.pt) Received: from gecea.ist.utl.pt (gecea.ist.utl.pt [193.136.140.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E81C43D6E for ; Tue, 6 Dec 2005 07:21:39 +0000 (GMT) (envelope-from brunomiguel@dequim.ist.utl.pt) Received: from [192.168.0.100] (c-66-30-11-146.hsd1.ma.comcast.net [66.30.11.146]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gecea.ist.utl.pt (Postfix) with ESMTP id 2BFC74102 for ; Tue, 6 Dec 2005 07:21:36 +0000 (WET) Message-ID: <43953BFD.6040409@dequim.ist.utl.pt> Date: Tue, 06 Dec 2005 02:21:33 -0500 From: Bruno Afonso User-Agent: Thunderbird 1.5 (Macintosh/20051025) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: mpt driver problem? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 07:21:44 -0000 Hi, I have a box that's running a scsi card that uses the mpt driver. This is now running 6.0: Dec 6 07:14:04 ribossoma kernel: mpt0: port 0xc400-0xc4ff mem 0xfea90000-0xfea9ffff,0xfea80000-0xfea8ffff irq 19 at device 3.0 on Dec 6 07:14:04 ribossoma kernel: mpt0: [GIANT-LOCKED] Dec 6 07:14:04 ribossoma kernel: mpt0: MPI Version=1.2.6.0 Dec 6 07:14:04 ribossoma kernel: mpt0: Unhandled Event Notify Frame. Event 0xa. Dec 6 07:14:04 ribossoma kernel: mpt0: Capabilities: ( RAID-1 SAFTE ) Dec 6 07:14:04 ribossoma kernel: mpt0: 0 Active Volumes (1 Max) Dec 6 07:14:04 ribossoma kernel: mpt0: 0 Hidden Drive Members (3 Max) Dec 6 07:14:04 ribossoma kernel: mpt1: port 0xc800-0xc8ff mem 0xfeaf0000-0xfeafffff,0xfeae0000-0xfeaeffff irq 18 at device 3.1 on Dec 6 07:14:04 ribossoma kernel: mpt1: [GIANT-LOCKED] Dec 6 07:14:04 ribossoma kernel: mpt1: MPI Version=1.2.6.0 Dec 6 07:14:04 ribossoma kernel: mpt1: Unhandled Event Notify Frame. Event 0xa. Dec 6 07:14:04 ribossoma kernel: mpt1: Capabilities: ( RAID-1 SAFTE ) Dec 6 07:14:04 ribossoma kernel: mpt1: 0 Active Volumes (1 Max) Dec 6 07:14:04 ribossoma kernel: mpt1: 0 Hidden Drive Members (3 Max) Dec 6 07:14:04 ribossoma kernel: da0 at mpt0 bus 0 target 0 lun 0 Dec 6 07:14:04 ribossoma kernel: da0: Fixed Direct Access SCSI-3 device Dec 6 07:14:04 ribossoma kernel: da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled Dec 6 07:14:04 ribossoma kernel: da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) The problem appears randomly on boots, meaning that it does not show indeed on EVERY boot, but afterwards, every so often. This is what typically appears: Dec 6 07:14:27 ribossoma kernel: mpt0: Request 0xc24755a8 Timed out. Dec 6 07:14:27 ribossoma kernel: mpt0: Attempting to Abort Req 0xc24755a8 Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): READ(10). CDB: 28 0 0 f0 88 87 0 0 48 0 Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): CAM Status: SCSI Status Error Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): SCSI Status: Check Condition Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2 Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): Scsi bus reset occurred field replaceable unit: 2 Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): Retrying Command (per Sense Data) Dec 6 07:14:28 ribossoma kernel: mpt0: Request 0xc2475508 Timed out. Dec 6 07:14:28 ribossoma kernel: mpt0: Attempting to Abort Req 0xc2475508 Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): READ(10). CDB: 28 0 0 f0 84 a7 0 0 28 0 Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): CAM Status: SCSI Status Error Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): SCSI Status: Check Condition Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2 Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): Scsi bus reset occurred field replaceable unit: 2 Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): Retrying Command (per Sense Data) Dec 6 07:14:30 ribossoma kernel: mpt0: Request 0xc24756c0 Timed out. Dec 6 07:14:30 ribossoma kernel: mpt0: Attempting to Abort Req 0xc24756c0 Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): READ(10). CDB: 28 0 0 ec cb af 0 0 40 0 Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): CAM Status: SCSI Status Error Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): SCSI Status: Check Condition Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2 Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): Scsi bus reset occurred field replaceable unit: 2 Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): Retrying Command (per Sense Data) I'd like to know if this is a serious problem with hardware or the driver itself. Should I worry? I know that some work is being done on mpt but I cannot use -current as this is a production box. I have used a -stable and it didn't improve so now I'm back to 6.0. I'll provide more information if needed. Thanks Bruno Afonso