From owner-freebsd-stable@FreeBSD.ORG Thu Sep 17 06:14:26 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 2B9C0106566C; Thu, 17 Sep 2009 06:14:26 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id 8C1078FC0A; Thu, 17 Sep 2009 06:14:25 +0000 (UTC) Received: by fxm6 with SMTP id 6so3796167fxm.43 for ; Wed, 16 Sep 2009 23:14:24 -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; bh=myCwIN++NT6Qm6DuGu9dU4kM499eCxrj3Q9n3gtPPrc=; b=VnLYLDEGVe+c3DK7o0SUJ9uihYj5HwibPUNDH88B4/yYS9Ft52Abgf+/UVxybcvjHv ObbiCREfDJSSZwPj91Ats4ySClAStGsOUaDnzKLNVaUqmoNF/NYT4xOtmtCe1PwLmWZ9 2Jt/QAA4/6sMEiivRu5/LyRpsgperNW0ScgxM= 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; b=XLyGX57zVC4wxaWMatE0AgOhdEOfhxbubHJ71TuCkUsTtp+9eERjAJ6tdjzYYZg1PZ TWJPZGOyVzU62Mv3B+VcUStPLtuOthVyBflzBMW9woFhXIgfhWIz3p4f24Ff81XrriC0 hYC4i9iQh+FNIFsdqh6SARa1PFzE/eanWz9LM= MIME-Version: 1.0 Received: by 10.204.19.132 with SMTP id a4mr50256bkb.21.1253168064360; Wed, 16 Sep 2009 23:14:24 -0700 (PDT) In-Reply-To: <20090617142952.GA73887@sandvine.com> References: <200906160830.29721.jhb@freebsd.org> <20090617142952.GA73887@sandvine.com> Date: Thu, 17 Sep 2009 10:14:24 +0400 Message-ID: From: pluknet To: Ed Maste Content-Type: text/plain; charset=ISO-8859-1 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: Thu, 17 Sep 2009 06:14:26 -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 > Sorry for late reply. Several months testing shows that in-tree aac(4) as of 6.4 (and later) has no this problem. Thanks. -- wbr, pluknet