From owner-freebsd-drivers@FreeBSD.ORG Mon Feb 14 14:56:25 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15255106566B for ; Mon, 14 Feb 2011 14:56:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C9FA88FC0C for ; Mon, 14 Feb 2011 14:56:24 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 482C146B06; Mon, 14 Feb 2011 09:56:24 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4E0898A01D; Mon, 14 Feb 2011 09:56:23 -0500 (EST) From: John Baldwin To: freebsd-drivers@freebsd.org Date: Mon, 14 Feb 2011 09:27:11 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <4D55BBDC.7000604@soe.ucsc.edu> In-Reply-To: <4D55BBDC.7000604@soe.ucsc.edu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201102140927.11654.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 14 Feb 2011 09:56:23 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=0.5 required=4.2 tests=BAYES_00,MAY_BE_FORGED, RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: Subject: Re: MFI Driver Behavior X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Feb 2011 14:56:25 -0000 On Friday, February 11, 2011 5:44:44 pm Erich Weiler wrote: > Hi All - I've posted on the forums but no one seems to have any ideas... > I have an odd lock up issue with a Perc H800 controller under > 8.2-PRERELEASE. > > We have a FreeBSD server running: > > Code: > > FreeBSD 8.2-PRERELEASE (GENERIC) #0: Thu Dec 16 14:59:46 PST 2010 > > It's a Dell R610. It has two MD1200 disk arrays on it, SAS chained > together. The controller that manages them is a Perc H800, with the > latest firmware available. > > I have the disks exported JBOD from the controller. And, the disks are > roped into a ZFS filesystem, which is exported via NFS to the local net. > > Everything works well most of the time, but every once in a while (like > once every few days), the filesystem completely hangs and we see these > errors on the console: > > mfi0: COMMAND 0xffffff80009b5870 TIMEOUT AFTER 61793 SECONDS > mfi0: COMMAND 0xffffff80009b5870 TIMEOUT AFTER 61823 SECONDS > mfi0: COMMAND 0xffffff80009b5870 TIMEOUT AFTER 61853 SECONDS > mfi0: COMMAND 0xffffff80009b5870 TIMEOUT AFTER 61923 SECONDS > > (this is after the filesystem has been hung for a day) > > etc... When I start poking around with mfiutil, it shows everything is > OK, the disks are all OK, the volumes are good, the event logs show no > errors. The "Patrol" feature is disabled. The battery is fine. > > After running "mfiutil show volumes", the lockup magically frees itself. > But, I don't want them to happen in the first place, and I certainly > don't want to have to manually run a "mfiutil show volumes" or whatever > to unlock it every time. Has anyone seen this before? > > I've actually tried another H800 controller we had on the shelf as well, > just to rule out a hardware problem with the first one, but we see the > same behavior on both controllers. > > "zpool status" also shows the disks as all OK, and a "zpool scrub" turns > up no problems. > > Any insight much appreciated!! Since multiple controllers exhibit the > same behavior, I was thinking it's falling more into a driver issue at > this point. I hope I'm right! I emailed the author of the MFI driver > for FreeBSD, but have not heard anything back, so I was hoping someone > here would have an idea of where I could turn next. > > If even there was a way I could determine what the "0xffffff80009b5870" > MFI command is, that would be a big help, so I would have a better idea > of where to continue my investigations. That value is just a pointer to the command structure in the device driver for the command that timed out. It probably is not that useful. The best person to ask about this is probably Scott Long (scottl@FreeBSD.org). The fact that 'show volumes' unsticks the controller sounds quite odd. Are you using MSI? If so, have you tried disabling MSI? -- John Baldwin From owner-freebsd-drivers@FreeBSD.ORG Mon Feb 14 23:31:52 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BDB2106564A for ; Mon, 14 Feb 2011 23:31:52 +0000 (UTC) (envelope-from weiler@soe.ucsc.edu) Received: from mail-01.cse.ucsc.edu (mail-01.cse.ucsc.edu [128.114.48.32]) by mx1.freebsd.org (Postfix) with ESMTP id 686468FC12 for ; Mon, 14 Feb 2011 23:31:52 +0000 (UTC) Received: from wraith.cse.ucsc.edu (wraith.cse.ucsc.edu [128.114.56.35]) by mail-01.cse.ucsc.edu (Postfix) with ESMTPSA id DD74A1009C06; Mon, 14 Feb 2011 15:31:51 -0800 (PST) Message-ID: <4D59BB67.1080703@soe.ucsc.edu> Date: Mon, 14 Feb 2011 15:31:51 -0800 From: Erich Weiler User-Agent: Thunderbird 2.0.0.24 (X11/20100318) MIME-Version: 1.0 To: John Baldwin References: <4D55BBDC.7000604@soe.ucsc.edu> <201102140927.11654.jhb@freebsd.org> In-Reply-To: <201102140927.11654.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-drivers@freebsd.org Subject: Re: MFI Driver Behavior X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Feb 2011 23:31:52 -0000 >> If even there was a way I could determine what the "0xffffff80009b5870" >> MFI command is, that would be a big help, so I would have a better idea >> of where to continue my investigations. > > That value is just a pointer to the command structure in the device driver for > the command that timed out. It probably is not that useful. The best person > to ask about this is probably Scott Long (scottl@FreeBSD.org). The fact that > 'show volumes' unsticks the controller sounds quite odd. Are you using MSI? > If so, have you tried disabling MSI? Thanks for replying! Yeah, I tried to contact Scott but it seems like he does not reply to user email (some others have mentioned this as well on the lists). But, I'm not sure about MSI. How would I confirm I'm using it, or disable it? It looks from a bit of googling that one can disable it by adding: hw.pci.enable_msix=0 hw.pci.enable_msi=0 to /boot/loader.conf, and rebooting. Would that do it? But would I lose anything by disabling MSI? I'm still not exactly sure what it does, even after googling a bit... ;) Is there a man page I can look at? Thanks for the help! From owner-freebsd-drivers@FreeBSD.ORG Tue Feb 15 12:51:49 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4ADFE1065674 for ; Tue, 15 Feb 2011 12:51:49 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1E4E88FC18 for ; Tue, 15 Feb 2011 12:51:49 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id CE25D46B35; Tue, 15 Feb 2011 07:51:48 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 0D8308A027; Tue, 15 Feb 2011 07:51:48 -0500 (EST) From: John Baldwin To: Erich Weiler Date: Tue, 15 Feb 2011 07:49:11 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <4D55BBDC.7000604@soe.ucsc.edu> <201102140927.11654.jhb@freebsd.org> <4D59BB67.1080703@soe.ucsc.edu> In-Reply-To: <4D59BB67.1080703@soe.ucsc.edu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201102150749.11413.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 15 Feb 2011 07:51:48 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=0.5 required=4.2 tests=BAYES_00,MAY_BE_FORGED, RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: freebsd-drivers@freebsd.org Subject: Re: MFI Driver Behavior X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2011 12:51:49 -0000 On Monday, February 14, 2011 6:31:51 pm Erich Weiler wrote: > >> If even there was a way I could determine what the "0xffffff80009b5870" > >> MFI command is, that would be a big help, so I would have a better idea > >> of where to continue my investigations. > > > > That value is just a pointer to the command structure in the device driver for > > the command that timed out. It probably is not that useful. The best person > > to ask about this is probably Scott Long (scottl@FreeBSD.org). The fact that > > 'show volumes' unsticks the controller sounds quite odd. Are you using MSI? > > If so, have you tried disabling MSI? > > Thanks for replying! Yeah, I tried to contact Scott but it seems like > he does not reply to user email (some others have mentioned this as well > on the lists). > > But, I'm not sure about MSI. How would I confirm I'm using it, or > disable it? It looks from a bit of googling that one can disable it by > adding: > > hw.pci.enable_msix=0 > hw.pci.enable_msi=0 > > to /boot/loader.conf, and rebooting. Would that do it? Yes. > But would I lose anything by disabling MSI? I'm still not exactly sure > what it does, even after googling a bit... ;) Is there a man page I > can look at? Hrmph. It looks like our in-tree mfi(4) driver does not support MSI after all. How odd. I know the hardware supports MSI. In that case, this test won't help. :( -- John Baldwin From owner-freebsd-drivers@FreeBSD.ORG Tue Feb 15 16:57:27 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80A8E106566C; Tue, 15 Feb 2011 16:57:27 +0000 (UTC) (envelope-from weiler@soe.ucsc.edu) Received: from mail-01.cse.ucsc.edu (mail-01.cse.ucsc.edu [128.114.48.32]) by mx1.freebsd.org (Postfix) with ESMTP id 6E9D58FC0C; Tue, 15 Feb 2011 16:57:27 +0000 (UTC) Received: from mail-01.cse.ucsc.edu (mail-01.cse.ucsc.edu [128.114.48.32]) by mail-01.cse.ucsc.edu (Postfix) with ESMTP id 195751009C1B; Tue, 15 Feb 2011 08:57:27 -0800 (PST) Date: Tue, 15 Feb 2011 08:57:27 -0800 (PST) From: Erich Weiler To: John Baldwin Message-ID: <1572482665.142375.1297789046999.JavaMail.root@mail-01.cse.ucsc.edu> In-Reply-To: <201102150749.11413.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [128.114.50.223] X-Mailer: Zimbra 6.0.9_GA_2686 (ZimbraWebClient - FF3.0 (Linux)/6.0.9_GA_2686) Cc: freebsd-drivers@freebsd.org Subject: Re: MFI Driver Behavior X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2011 16:57:27 -0000 > > But would I lose anything by disabling MSI? I'm still not exactly > > sure > > what it does, even after googling a bit... ;) Is there a man page I > > can look at? > > Hrmph. It looks like our in-tree mfi(4) driver does not support MSI > after > all. How odd. I know the hardware supports MSI. In that case, this > test > won't help. :( We are testing a new theory. We believe that the C-states and C1E control on this chipset (in the Dell R610), which are configurable in the BIOS, are affecting the controller in some way. We are disabling them and trying again. I'll post results soon. From owner-freebsd-drivers@FreeBSD.ORG Tue Feb 15 17:25:41 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73F73106566C for ; Tue, 15 Feb 2011 17:25:41 +0000 (UTC) (envelope-from attila.bogar@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 073DF8FC1B for ; Tue, 15 Feb 2011 17:25:40 +0000 (UTC) Received: by fxm16 with SMTP id 16so419787fxm.13 for ; Tue, 15 Feb 2011 09:25:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=kE4Y4eBQ49Chaw5+QlKahaUZlXXjd+ZcX3C2QHMpd9E=; b=HmESVxiz5+rk9Ce7La11SlFD8Mr7oS8im+QVIOrfDDON/v0MnVzVS+I8AkDjrXqPlW ROIpfpa5AwD+PAt17CN5IkLMbwS7eQ6KtDWkAL3j8G3Esyx98HCqzZHoh3qHgpQtlUsh jXP2xziZ9dq5FxP9g7wX1bBVdkix/f9oIKIZM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=JKCDXWqVCUELf/Cs5ve+BQ9ptZejQ4F1ZiOvjN/5W7vmuHqGT5uVR2LlTWKJTLWAN8 hk7PQDCLQkNL/ldhWOu9jjFgNDzGJqGB/bEkJusgQHjWZjN6A/Dgyn9kYgeTAWptjiyo WkFkq3Knml9AFpm+VKwEVkp17ArcQD38+xf8Y= Received: by 10.223.81.68 with SMTP id w4mr6480332fak.84.1297789351381; Tue, 15 Feb 2011 09:02:31 -0800 (PST) Received: from [10.252.10.91] ([193.34.186.85]) by mx.google.com with ESMTPS id n3sm1765848faa.5.2011.02.15.09.02.28 (version=SSLv3 cipher=OTHER); Tue, 15 Feb 2011 09:02:29 -0800 (PST) Message-ID: <4D5AB1A3.4040109@gmail.com> Date: Tue, 15 Feb 2011 17:02:27 +0000 From: =?ISO-8859-1?Q?Attila_Bog=E1r?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-drivers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: mps and Dell PERC H200 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2011 17:25:41 -0000 Dear list, On a Dell R515 with a Dell PERC H200 Integrated we have 14 disks in JBOD behind the SAS expander. This card has a LSI SAS 2008 chip and is handled by the mps driver from HEAD. Unfortunately the mps picks up only 8 disks out of the 14. The Linux mpt2sas driver picks up all 14 drives. If I replace the H200 with an LSI MegaRAID SAS 9240-8i, then all 14 drives can be seen by the mfi driver from LSI's site. I'm experimenting with 8.2-RC3 + mps module from HEAD. I've already contacted Scott Long, but I haven't got a reply yet. I enabled mps debug information and added a few lines of extra debug info. The trace is available at http://www.linguamatics.com/debug/mps-trace-1.txt Try grep-in' for these words: EXTRA or Failure or Found The EXTRA lines have been added by me. I can see in the trace that probe succeeds on handles 0x000a .. 0x0012, but fails on the others. I've already tried to ignoring probes in this range by inserting an "if" clause to the code to see if this is a controller overrun problem, but the result is the same: no drives can be found on the other handles. The error code 0x0022 corresponds to MPI2_IOCSTATUS_BUSY|MPI2_IOCSTATUS_CONFIG_INVALID_ACTION. I can't see, that MPI2_IOCSTATUS_BUSY is handled during the probe phase. I've checked mpt2sas in Linux. That driver is marking the drive state with a SCSI BUSY flag (and maybe retrying later?)... What can be the problem? Any hints how to proceed? Thanks, Attila From owner-freebsd-drivers@FreeBSD.ORG Thu Feb 17 16:43:29 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81F46106566C; Thu, 17 Feb 2011 16:43:29 +0000 (UTC) (envelope-from weiler@soe.ucsc.edu) Received: from mail-01.cse.ucsc.edu (mail-01.cse.ucsc.edu [128.114.48.32]) by mx1.freebsd.org (Postfix) with ESMTP id 6EDB18FC14; Thu, 17 Feb 2011 16:43:29 +0000 (UTC) Received: from wraith.cse.ucsc.edu (wraith.cse.ucsc.edu [128.114.56.35]) by mail-01.cse.ucsc.edu (Postfix) with ESMTPSA id C10831009C34; Thu, 17 Feb 2011 08:43:28 -0800 (PST) Message-ID: <4D5D5030.5020904@soe.ucsc.edu> Date: Thu, 17 Feb 2011 08:43:28 -0800 From: Erich Weiler User-Agent: Thunderbird 2.0.0.24 (X11/20100318) MIME-Version: 1.0 To: John Baldwin References: <1572482665.142375.1297789046999.JavaMail.root@mail-01.cse.ucsc.edu> In-Reply-To: <1572482665.142375.1297789046999.JavaMail.root@mail-01.cse.ucsc.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-drivers@freebsd.org Subject: Re: MFI Driver Behavior X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2011 16:43:29 -0000 > We are testing a new theory. We believe that the C-states and C1E control on this chipset (in the Dell R610), which are configurable in the BIOS, are affecting the controller in some way. We are disabling them and trying again. I'll post results soon. After disabling C-states and CIE in the BIOS on our R610, the Perc H800 controller now appears stable. My ZFS filesystem appears stable. Life seems good. I wonder what those items in the BIOS are doing in relation to the kernel to cause this. From owner-freebsd-drivers@FreeBSD.ORG Thu Feb 17 17:00:08 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03F871065697 for ; Thu, 17 Feb 2011 17:00:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9A8E68FC1A for ; Thu, 17 Feb 2011 17:00:07 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 57DFE46B1A; Thu, 17 Feb 2011 12:00:07 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A2C998A009; Thu, 17 Feb 2011 12:00:06 -0500 (EST) From: John Baldwin To: Erich Weiler Date: Thu, 17 Feb 2011 11:53:29 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <1572482665.142375.1297789046999.JavaMail.root@mail-01.cse.ucsc.edu> <4D5D5030.5020904@soe.ucsc.edu> In-Reply-To: <4D5D5030.5020904@soe.ucsc.edu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201102171153.29396.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 17 Feb 2011 12:00:06 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=0.5 required=4.2 tests=BAYES_00,MAY_BE_FORGED, RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: freebsd-drivers@freebsd.org Subject: Re: MFI Driver Behavior X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2011 17:00:08 -0000 On Thursday, February 17, 2011 11:43:28 am Erich Weiler wrote: > > We are testing a new theory. We believe that the C-states and C1E control on this chipset (in the Dell R610), which are configurable in the BIOS, are affecting the controller in some way. We are disabling them and trying again. I'll post results soon. > > After disabling C-states and CIE in the BIOS on our R610, the Perc H800 > controller now appears stable. My ZFS filesystem appears stable. Life > seems good. > > I wonder what those items in the BIOS are doing in relation to the > kernel to cause this. Well, you can miss clock interrupts which might prevent timeout routines from firing (or they would fire too late). 9 has several changes that should support C1E properly I think. -- John Baldwin