From owner-freebsd-stable@FreeBSD.ORG Fri Jun 19 05:38:06 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 151E6106568D; Fri, 19 Jun 2009 05:38:06 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 324168FC15; Fri, 19 Jun 2009 05:38:04 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by bwz9 with SMTP id 9so15658bwz.43 for ; Thu, 18 Jun 2009 22:38:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=i2kcoF+LwScWaQ1af+875zGaYe+/IBYLeG14vrp7fl4=; b=jOCr+LwVYzjkYpJogx6k6DJYwzGBHbeOXyka+sAixRY0Y26L4YFKyG5uluqHezyzby bxOhAJCKM2N1c3ZfdzQi55ipXaaLB+W2DZys4H5zxE2au4FkZEm6LGD24bexScDUXaV0 1CUQnUWj8uA5xtPa8rA3L0kHTCw6k94Ry3pqA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ugHArufpDT2mWthGxorLYkLd0/A9oFv3+V7X3axfKc20FMlrno9/91+txTLzgjym76 MWWg1zel+ogmKJJpmoR0Db9+meS9KHU3UGrpHe8pik/MUWEu4qgzqD1CAfYo47BZZSMW ONp1ephMVNtF6T7+ubQkmDaMviqDFxKb/hKlQ= MIME-Version: 1.0 Received: by 10.103.52.13 with SMTP id e13mr1543462muk.46.1245389883940; Thu, 18 Jun 2009 22:38:03 -0700 (PDT) In-Reply-To: References: <200906160830.29721.jhb@freebsd.org> <20090617142952.GA73887@sandvine.com> Date: Fri, 19 Jun 2009 09:38:03 +0400 Message-ID: From: pluknet To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, Ed Maste Subject: Re: 6.2 sporadically locks up X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2009 05:38:06 -0000 2009/6/19 Adrian Chadd : > Just modify the driver slightly to hijack a different device prefix :) > Hi, Adrian. That's where I just go if I should have to. - .d_name =3D "aac", + .d_name =3D "aacu", (or vise versa) While here, I'd like to give some summary about locking up with "irq17:bce1 aacu0" vs arcconf scenario. Abstract: we have a number of boxes with IBM ServeRAID 8k on 6.2. That scenario takes place only with aacu b15753, and not with b15411 (at least not noticed). We take a decision some time ago to move some boxes to 6.4 (and leave vendor aacu b15753 there as it's) to see how it goes. Until now (2 or 3 weeks) there were no lockup. I hope it will so farther.. > > > Adrian > > 2009/6/17 pluknet : >> 2009/6/17 Ed Maste : >>> On Tue, Jun 16, 2009 at 07:03:34PM +0400, pluknet wrote: >>> >>>> As for allpcpu, I often see the picture, when one CPU runs the "irq17: >>>> bce1 aacu0" thread >>>> and another one runs arcconf. I wonder if that might be a source of >>>> bad locking or races, or.. >>>> The arcconf utility uses ioctl that goes into aac/aacu(4) internals. >>> >>> Do you see the same result w/ the in-tree aac(4) driver as opposed to >>> Adaptec's version? >>> >>> -Ed >>> >> >> [It's quite hard to move back to aac(4) as that requires fstab update >> [ aacdu0 -> aacd0] >> =A0and instant reboot, because we use quotas and quotacheck looks into /= etc/fstab. >> Such preparations as fstab update and commenting out load_aacu=3D"YES" w= ill give >> discrepancy between fstab and actual mount points.] >> >> I will try anyway. Thank you for your help. >> --=20 wbr, pluknet