From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 12:45:33 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 414461065672 for ; Sun, 11 Jan 2009 12:45:33 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id F10FC8FC13 for ; Sun, 11 Jan 2009 12:45:32 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LLzgr-0004Gu-Pk; Sun, 11 Jan 2009 12:45:17 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LLzgr-00008v-Nu; Sun, 11 Jan 2009 12:45:17 +0000 To: heliocentric@gmail.com In-Reply-To: Message-Id: From: Pete French Date: Sun, 11 Jan 2009 12:45:17 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking 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: Sun, 11 Jan 2009 12:45:33 -0000 > I noticed a similar problem testing 7.1-RC1, It seemed to be a deep > deadlock, as it was triggered by lighttpd doing kern_sendfile, and > never returning. The side effects (being unable to create processes, > etc) is similar. Interesting - did you get any responses from anyone else regarding this ? My last box which locked up was essentialy idle, so I am very surprised by all of this - also none of the heavilt loaded machines (i.e. the actual webservers) have locked up. I am also surprised that this isn't more widely reported, as the hardware is very common. The only oddity with ym compile is that I set the CPUTYPE to 'core2' - that shouldnt have an effect, but I will remove it anyway, just so I am actually building a completely vanilla amd64. That way I should have what everyone else has, and since I don't see anyone else saying they have isues then maybe mine will go away too (fingers crossed) > My kernconf is below, try building the kernel, and send an email > containing the backtrace from any process that has blocked (in my OK, will do. I can try this on the one non-essential box which locked up yesterday. I don't know how long it will before it locks up again, but will see if I can do some things to provoke it. -pete.