From owner-freebsd-stable@FreeBSD.ORG Wed Jun 17 14:45:58 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 A790B1065696 for ; Wed, 17 Jun 2009 14:45:58 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-bw0-f211.google.com (mail-bw0-f211.google.com [209.85.218.211]) by mx1.freebsd.org (Postfix) with ESMTP id 307588FC18 for ; Wed, 17 Jun 2009 14:45:57 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by bwz7 with SMTP id 7so366359bwz.43 for ; Wed, 17 Jun 2009 07:45:57 -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=0HDexferChNyTPLIRh0IKjtThmDNXD4SZTHhip7zH5U=; b=HbID7S9ce5rF/ADlrYFw/QU58++NLhXDkvBzc6MKse0CXNgIHX1yxoCWtZW/dHBv8g m5Zo/Fjuupfo91GUqJyxAGrM5+9qez+SJdGgtQeyfqi9WaZlOkrGWKp25AnG0aXyQeYA X09UZJ5j3tjMVFjkEhWEA/BGVVzuMeHVGYhIc= 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=mOSWYwfnGPv+N783UUBcZ+koctDz0PWQqMIaAztmIY7E7OnM2Guxsl6AT8H6tmW11C bMQm1IVXCr5dcRbOAwyQFWKH6mmVlomGP21Dx2Hhm+eZ+YvNyyFjzIod7GX0yZuAZtBl VJnrr8W7VyRGNj0H7S5KZD60B4VkEtlLmM4SE= MIME-Version: 1.0 Received: by 10.103.160.9 with SMTP id m9mr177968muo.53.1245249956871; Wed, 17 Jun 2009 07:45:56 -0700 (PDT) In-Reply-To: <20090617142952.GA73887@sandvine.com> References: <200906160830.29721.jhb@freebsd.org> <20090617142952.GA73887@sandvine.com> Date: Wed, 17 Jun 2009 18:45:56 +0400 Message-ID: From: pluknet To: Ed Maste Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org 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: Wed, 17 Jun 2009 14:45:59 -0000 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] and instant reboot, because we use quotas and quotacheck looks into /etc/fstab. Such preparations as fstab update and commenting out load_aacu="YES" will give discrepancy between fstab and actual mount points.] I will try anyway. Thank you for your help. -- wbr, pluknet