From owner-freebsd-current@FreeBSD.ORG Tue Jun 3 09:24:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08E5B37B401 for ; Tue, 3 Jun 2003 09:24:41 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2551A43F85 for ; Tue, 3 Jun 2003 09:24:41 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h53GJcZ03210; Tue, 3 Jun 2003 09:19:38 -0700 Received: from freebsd.org (hollin.btc.adaptec.com [10.100.253.56]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id JAA07477; Tue, 3 Jun 2003 09:24:40 -0700 (PDT) Message-ID: <3EDCCB27.5020707@freebsd.org> Date: Tue, 03 Jun 2003 10:21:59 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bryan Liesner References: <20030602230746.U69975-100000@mail.chesapeake.net> <20030603115912.Q648@gravy.homeunix.net> In-Reply-To: <20030603115912.Q648@gravy.homeunix.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Jeff Roberson cc: current@freebsd.org Subject: Re: umtx/libthr SMP fixes. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2003 16:24:42 -0000 Bryan Liesner wrote: > On Mon, 2 Jun 2003, Jeff Roberson wrote: > > >>If you have had issues with libthr on SMP or umtx panics, the following >>patch may solve these issues. >> >>http://www.chesapeake.net/~jroberson/umtxlocks.diff >> >>This patch fixes several race conditions and other issues with umtx. > > > Actually, no it doesn't. I was able to use kern_umtx v 1.3 only if I > removed atapicam from my kernel config. These patches (now > committed?) panic the system whether I use atapicam or not. > With kern_umtx v1.2 there is no panic at all, with or without > atapicam. > > Actually, I think it's cam in general that's causing the panic with > these changes. > > Please see kern/52718 I didn't see a backtrace in the PR. Is there one that you can share with us? Scott