From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 22:33:00 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13A7C106564A for ; Tue, 26 Jun 2012 22:33:00 +0000 (UTC) (envelope-from rsimmons0@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id C1C8F8FC08 for ; Tue, 26 Jun 2012 22:32:59 +0000 (UTC) Received: by vbmv11 with SMTP id v11so356451vbm.13 for ; Tue, 26 Jun 2012 15:32:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LAd0XbttwyU7EUzgKl//PACI5VFUQugdMh4cF+KIqHM=; b=KfSzUvSjhGtbZ+RGSS63o0sGuqchvcsYQtEFsO0mSqkcYVOgfN3SGLto423P1fh+0K dvmtz3+Fqz/ZZxkyx1BCZOk2czqFPtCf9Sd8dfdfErxykC4mXj6vU860nRPFbVW/dXu/ sqvpja+H1xXI6VWdLbzqkhbGwmG5ss1JHsDhZPs3CxrNKiQE4mwWiesIdrRmXgCxdJ3K iHCUOhd/mzDRpcWFsgrKpmd8C4VXixjwjt0lsbQYhkiOfS2utlfDxB/s+2QU783IezDR 7Qz1GZpDVlpHV15xsYEOAmFSlM6WFNCnNrIiGbYbpmTwZq6FOBGexGlBw1Dlx1Db7ooo /GYQ== MIME-Version: 1.0 Received: by 10.52.94.109 with SMTP id db13mr10337750vdb.4.1340749979125; Tue, 26 Jun 2012 15:32:59 -0700 (PDT) Received: by 10.52.16.148 with HTTP; Tue, 26 Jun 2012 15:32:58 -0700 (PDT) Date: Tue, 26 Jun 2012 18:32:58 -0400 Message-ID: From: Robert Simmons To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Freeze when running freebsd-update X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2012 22:33:00 -0000 I've run into a totally reproducible freeze in 9.0. There are a number of variables involved, but I'm able to reproduce this freeze 100% of the time. I'm installing very small servers in a Xen HVM virtualization environment. Each instance has 128M memory and 4G of disk space. There is 384M of swap encrypted using geli_swap_flags="-d -l 256 -s 4096". The rest of the disk space is encrypted with "geli init -b -v -a hmac/sha256 -l 256 -s 4096 /dev/ada0p4". After I've installed a VPS in this way, I run the freebsd-update fetch command and it freezes at: Applying patches... I've been trying to diagnose the problem by running top and watching what happens during this stage. I noticed the following: 1) the box runs out of physical memory at this stage (totally expected, that's why there is sufficient swap space). 2) All the processes except 2 sleep: 31 processes: 1 running, 29 sleeping, 1 waiting 3) the box is responsive to hitting enter at the console (it produces another login: prompt) 4) sshd is asleep, so I can't ssh into the box 5) if I try to login to the console, it lets me enter a username then locks up totally, it does not present me with a password: prompt. 6) it has not run out of swap, nowhere close: Mem: 54M Active, 9524K Inact, 41M Wired, 24K Cache, 21M Buf, 32K Free Swap: 384M Total, 6452K Used, 378M Free, 1% Inuse 7) the moment it runs out of physical memory it begins being unresponsive Any idea what might be going on here?