From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 26 18:17:31 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71EAB1065670 for ; Wed, 26 Sep 2012 18:17:31 +0000 (UTC) (envelope-from Paul.Maulberger@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id D09618FC08 for ; Wed, 26 Sep 2012 18:17:30 +0000 (UTC) Received: (qmail 8653 invoked by uid 0); 26 Sep 2012 18:17:24 -0000 Received: from 31.17.21.234 by www021.gmx.net with HTTP; Wed, 26 Sep 2012 20:17:23 +0200 (CEST) Content-Type: text/plain; charset="utf-8" Date: Wed, 26 Sep 2012 20:17:23 +0200 From: "Paul Maulberger" In-Reply-To: Message-ID: <20120926181723.327430@gmx.net> MIME-Version: 1.0 References: <20120923140816.144270@gmx.net> <20120926093759.299750@gmx.net> To: Jim Harris X-Authenticated: #143783428 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1+HhhE0bpiHaiNXgYnh0XxRUpVvAEqPd5u+XJfZdN j5ktg2cW2SFY3HBlkqfw/as+8uAY7SpSy+PA== Content-Transfer-Encoding: 8bit X-GMX-UID: 5CMRcIMeeSEqQ2WV+nwhMkZ+IGRvb0Ag Cc: freebsd-scsi@freebsd.org Subject: Re: Intel C600 SAS Controller + locate LED (SGPIO) 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: Wed, 26 Sep 2012 18:17:31 -0000 Hi Folks, I do not share Jim's opinion. I think the fault led should be access-able by the userspace. I have a special system monitor daemon which although checks the S.M.A.R.T. information of the hard drive. If information X is above value Y the system monitor daemon informs the admin and sets the fault led. In this case the driver could not set the fault led because it does not know "my" value Y. As the fault led is rarely set the userspace and the driver should have shared access to the led. Also a conflict could be easily solved: solution a: The last one wins. solution b: If the driver sets the fault led the userspace could not clear it. What do you think? Regards Paul -------- Original-Nachricht -------- > Datum: Wed, 26 Sep 2012 08:57:13 -0700 > Von: Jim Harris > An: Paul Maulberger > CC: freebsd-scsi@freebsd.org > Betreff: Re: Intel C600 SAS Controller + locate LED (SGPIO) > On Wed, Sep 26, 2012 at 2:37 AM, Paul Maulberger > wrote: > > Hi Jim, > > > > your patch is working very well. Thanks a lot! > > > > To support the locate and the fault led I extended your patch a little > bit. Like the ahci driver every port has now a locate and a fault led > device. > > Hi Paul, > > I am reluctant to add LEDs for error, even though I know AHCI driver > does this today. I don't see the need for userspace to manipulate > both locate and error LEDs - it seems locate is sufficient. I'd > prefer to keep error LED reserved for future use in the driver. > > But I will add "locate" to the LED name, just to make it more clear. > > > # ls -al /dev/led > > total 1 > > dr-xr-xr-x 2 root wheel 512 Sep 26 08:39 . > > dr-xr-xr-x 11 root wheel 512 Sep 26 10:39 .. > > crw------- 1 root wheel 0, 47 Sep 26 08:43 ahcich0.fault > > crw------- 1 root wheel 0, 46 Sep 26 08:44 ahcich0.locate > > crw------- 1 root wheel 0, 49 Sep 26 08:39 ahcich1.fault > > crw------- 1 root wheel 0, 48 Sep 26 08:39 ahcich1.locate > > crw------- 1 root wheel 0, 51 Sep 26 08:39 ahcich2.fault > > crw------- 1 root wheel 0, 50 Sep 26 08:39 ahcich2.locate > > crw------- 1 root wheel 0, 53 Sep 26 08:39 ahcich3.fault > > crw------- 1 root wheel 0, 52 Sep 26 08:39 ahcich3.locate > > crw------- 1 root wheel 0, 55 Sep 26 08:39 ahcich4.fault > > crw------- 1 root wheel 0, 54 Sep 26 08:39 ahcich4.locate > > crw------- 1 root wheel 0, 57 Sep 26 08:44 ahcich5.fault > > crw------- 1 root wheel 0, 56 Sep 26 08:44 ahcich5.locate > > crw------- 1 root wheel 0, 36 Sep 26 08:39 igb0 > > crw------- 1 root wheel 0, 37 Sep 26 08:39 igb1 > > crw------- 1 root wheel 0, 38 Sep 26 08:39 isci.bus0.port0.fault > > crw------- 1 root wheel 0, 39 Sep 26 08:39 isci.bus0.port0.locate > > crw------- 1 root wheel 0, 40 Sep 26 08:42 isci.bus0.port1.fault > > crw------- 1 root wheel 0, 41 Sep 26 08:42 isci.bus0.port1.locate > > crw------- 1 root wheel 0, 42 Sep 26 08:39 isci.bus0.port2.fault > > crw------- 1 root wheel 0, 43 Sep 26 08:39 isci.bus0.port2.locate > > crw------- 1 root wheel 0, 44 Sep 26 08:39 isci.bus0.port3.fault > > crw------- 1 root wheel 0, 45 Sep 26 08:39 isci.bus0.port3.locate > > > > By the way the main board X9DRi-F has only one bus. The X9DR3-F has 2 > buses. > > > > The patch (compared to 9.1 RC1) is attached. > > > > Is it possible to commit this patch into 9.1 or is it too late? > > I think it is too late. The changes here are very low risk, but it is > a new feature and not a bug fix so not really appropriate for 9.1 at > this point. > > Thank you for testing the patch! > > Regards, > > -Jim > > > > Regards > > Paul > > > > Hint: If anybody is using a SC825TQ chassis and no led is blinking check > ALL jumper settings of your backplane (Appendix C of > http://www.supermicro.com/manuals/chassis/2U/SC825.pdf). Our backplane was wrongly configured by > factory (mixture of sgpio and i2c settings). > > > >