From owner-freebsd-questions@FreeBSD.ORG Tue Jun 26 23:11:58 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D2AC106566B for ; Tue, 26 Jun 2012 23:11:58 +0000 (UTC) (envelope-from rsimmons0@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id BD35D8FC0A for ; Tue, 26 Jun 2012 23:11:57 +0000 (UTC) Received: by vcbfy7 with SMTP id fy7so385449vcb.13 for ; Tue, 26 Jun 2012 16:11:51 -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=FDvxSM9zY/V/9LqCKD5731lvwHibAnIs27UTcPTM/2Y=; b=AIEjPiq1DkdKNJOOv3i101cAsS+8AUNhgH0kEnSAJGcUmQnZqXmCrd37xxZccTAAKS 0g4G6jNN2AvcnfqUj9Qg+FjroIidxy+xnjfjjiYwsQAIa9pcuf7LS4+Pfs9o1Q0BKAC/ 0xR0hkzTSPTWYohrPdufE22DjSXeZVR6vbW+vFiI6IfjSAmYTVhT/iaU+g/ElQI3Lc1k Onz85q7cQ3rI1GUE3cGUueAmcafaJZxKYPUtXg8MkIICPdO3rAJmRGbr9DnfMsXs7i90 bdmZWh6r7sL5q9z2LtKGAFbbVZMyayYAQ5O0mT6f/jxEDLhJokjD0FenR3BG4jCNvx2A sZyg== MIME-Version: 1.0 Received: by 10.52.28.202 with SMTP id d10mr10361518vdh.39.1340752311578; Tue, 26 Jun 2012 16:11:51 -0700 (PDT) Received: by 10.52.16.148 with HTTP; Tue, 26 Jun 2012 16:11:51 -0700 (PDT) Date: Tue, 26 Jun 2012 19:11:51 -0400 Message-ID: From: Robert Simmons To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Freeze when running freebsd-update X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2012 23:11:58 -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?