From owner-freebsd-threads@FreeBSD.ORG Fri Jan 2 00:47:25 2009 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78573106564A; Fri, 2 Jan 2009 00:47:25 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 67FBA8FC18; Fri, 2 Jan 2009 00:47:25 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 5CE901A3C39; Thu, 1 Jan 2009 16:32:15 -0800 (PST) Date: Thu, 1 Jan 2009 16:32:15 -0800 From: Alfred Perlstein To: David Xu , Julian Elischer , threads@freebsd.org Message-ID: <20090102003215.GB60686@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: (forw) Re: (forw) Re: Process stuck in STOP state X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2009 00:47:25 -0000 David, Julian, there's a pretty good synopsys by Tor attached here for a deadlock in 7.x. Can anyone comment if it's fixed or if there's a way to fix it? thanks, -Alfred ----- Forwarded message from Tor Egge ----- From: Tor Egge To: alfred@freebsd.org Cc: smp@freebsd.org Subject: Re: (forw) Re: Process stuck in STOP state Date: Thu, 01 Jan 2009 22:15:14 +0000 (UTC) Message-Id: <20090101.221514.41667097.Tor.Egge@cvsup.no.freebsd.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Sender: owner-freebsd-smp@freebsd.org > Can someone look at this? This is pretty weird, it seems > that somehow there's some deadlock with vnode locks, but it > doesn't appear to be due a leaked vnode lock as "show lockednods" > doesn't show any vnodes locks. > > The trace should be somewhat easy to figure out but I'm kinda > of stuck.. > > Any ideas how this could happen? I had a brief look at msgbuf.txt contained info about some nfs vnodes locked by pid 27645. It looks like thread suspension is broken for the SINGLE_NO_EXIT case. Threads performing an interruptable sleep are suspended, even while holding other resources (e.g. vnode locks). Threads performing a non-interruptable sleep, waiting for resources held by the suspended threads are not suspended. The thread that started the suspension is not woken up since some of the other threads are not yet suspended. - Tor Egge _______________________________________________ freebsd-smp@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-smp To unsubscribe, send any mail to "freebsd-smp-unsubscribe@freebsd.org" ----- End forwarded message ----- -- - Alfred Perlstein From owner-freebsd-threads@FreeBSD.ORG Fri Jan 2 20:10:08 2009 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42AAA10656C8 for ; Fri, 2 Jan 2009 20:10:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 152CA8FC16 for ; Fri, 2 Jan 2009 20:10:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n02KA7Qt047339 for ; Fri, 2 Jan 2009 20:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n02KA7J9047338; Fri, 2 Jan 2009 20:10:07 GMT (envelope-from gnats) Date: Fri, 2 Jan 2009 20:10:07 GMT Message-Id: <200901022010.n02KA7J9047338@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Ed Maste Cc: Subject: Re: threads/129956: Threaded process stuck in "vmopar" state, other in "ufs" later. X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ed Maste List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2009 20:10:08 -0000 The following reply was made to PR threads/129956; it has been noted by GNATS. From: Ed Maste To: bug-followup@FreeBSD.org, pluknet@gmail.com Cc: Subject: Re: threads/129956: Threaded process stuck in "vmopar" state, other in "ufs" later. Date: Fri, 2 Jan 2009 15:01:04 -0500 > ino 68191367, on dev aacdu0s1g aacdu implies that you're using Adaptec's vendor driver; can you confirm this and provide the build number of the driver you're using? -Ed From owner-freebsd-threads@FreeBSD.ORG Sat Jan 3 08:40:03 2009 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A7AE1065670 for ; Sat, 3 Jan 2009 08:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 228E78FC1B for ; Sat, 3 Jan 2009 08:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n038e2E0050812 for ; Sat, 3 Jan 2009 08:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n038e2oR050808; Sat, 3 Jan 2009 08:40:02 GMT (envelope-from gnats) Date: Sat, 3 Jan 2009 08:40:02 GMT Message-Id: <200901030840.n038e2oR050808@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: pluknet Cc: Subject: Re: threads/129956: Threaded process stuck in "vmopar" state, other in "ufs" later. X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pluknet List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jan 2009 08:40:03 -0000 The following reply was made to PR threads/129956; it has been noted by GNATS. From: pluknet To: "Ed Maste" Cc: bug-followup@freebsd.org Subject: Re: threads/129956: Threaded process stuck in "vmopar" state, other in "ufs" later. Date: Sat, 3 Jan 2009 11:30:09 +0300 Ed, I'm going to provide more info about this issue (currently far away from console, xmas vacations..). Yes. It's unmodified vendor aacu driver @ IBM ServeRAID 8k at brand new x3650. From arcconf: -------------------------------------------------------- Controller Version Information -------------------------------------------------------- BIOS : 5.2-0 (15421) Firmware : 5.2-0 (15421) Driver : 2.1-15 (15753) Boot Flash : 5.1-0 (15411) -------------------------------------------------------- -- wbr, pluknet