From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 20 09:31:03 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE7F9106568D for ; Wed, 20 Jan 2010 09:31:03 +0000 (UTC) (envelope-from stephane.lapie@darkbsd.org) Received: from quasar.darkbsd.org (shinigami.darkbsd.org [82.227.96.182]) by mx1.freebsd.org (Postfix) with ESMTP id A62C28FC12 for ; Wed, 20 Jan 2010 09:31:03 +0000 (UTC) Received: from quasar.darkbsd.org (localhost [127.0.0.1]) by quasar.darkbsd.org (Postfix) with ESMTP id 8FB9016EA for ; Wed, 20 Jan 2010 10:30:56 +0100 (CET) Received: from quasar.darkbsd.org ([127.0.0.1]) by quasar.darkbsd.org (quasar.darkbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZLOxBuOPmWE for ; Wed, 20 Jan 2010 10:30:54 +0100 (CET) Received: from [192.168.166.29] (unknown [210.188.173.245]) (Authenticated sender: darksoul) by quasar.darkbsd.org (Postfix) with ESMTPSA id 9362F16E3 for ; Wed, 20 Jan 2010 10:30:53 +0100 (CET) Message-ID: <4B56CD4C.80503@darkbsd.org> Date: Wed, 20 Jan 2010 18:30:52 +0900 From: Stephane LAPIE User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org X-Enigmail-Version: 0.96.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE7F1DEF35E2B614F39635BA7" Subject: DELL SAS5/E Controller bug X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jan 2010 09:31:04 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE7F1DEF35E2B614F39635BA7 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello list, Basically I'm experiencing the same problem as described here : https://forums.freebsd.org/showthread.php?t=3D9407 (linking for reference= ) Drives disconnections are not recognized instantly, and instead I get the following dmesg entries : mpt0: mpt_cam_event: 0x16 mpt0: mpt_cam_event: 0x16 (Sometimes I also get "mpt0: mpt_cam_event: 0x12" events) This is really crippling as this litterally paralyzes the ZFS pool until the controller finally comes to its senses (...or until a disk gets replugged in, which provokes a flush of all the buffered failed SCSI requests). Hardware is recognized as : mpt0@pci0:6:8:0: class=3D0x010000 card=3D0x1f041028 chip=3D0x00541000 rev= =3D0x01 hdr=3D0x00 vendor =3D 'LSI Logic (Was: Symbios Logic, NCR)' device =3D 'SAS 3000 series, 8-port with 1068 -StorPort' class =3D mass storage subclass =3D SCSI Did anyone else experience this, or find a proper work-around ? Thanks in advance for your time, --=20 Stephane LAPIE, EPITA SRS, Promo 2005 "Even when they have digital readouts, I can't understand them." --MegaTokyo --------------enigE7F1DEF35E2B614F39635BA7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktWzU0ACgkQ24Ql8u6TF2PHOwCg72hxd9fwISEgt4OAVTbRiBuS FTwAoJuIQL3kYlmtXN48swDcHulk8YDK =7jM8 -----END PGP SIGNATURE----- --------------enigE7F1DEF35E2B614F39635BA7--