From owner-freebsd-current@FreeBSD.ORG Sat Jun 28 03:41:43 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7DEBBA6D for ; Sat, 28 Jun 2014 03:41:43 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B7332C70 for ; Sat, 28 Jun 2014 03:41:42 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id C80B91FE02D; Sat, 28 Jun 2014 05:41:41 +0200 (CEST) Message-ID: <53AE3989.9020000@selasky.org> Date: Sat, 28 Jun 2014 05:42:01 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Danilo Egea , "freebsd-current@freebsd.org" Subject: Re: sysctl: Cannot allocate memory after r267961 References: <1403895102.10070.YahooMailNeo@web162001.mail.bf1.yahoo.com> In-Reply-To: <1403895102.10070.YahooMailNeo@web162001.mail.bf1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Sat, 28 Jun 2014 03:41:43 -0000 On 06/27/14 20:51, Danilo Egea wrote: > Hello folks, > > I've just updated my system (current) and now I'm getting this message: > [danilo src$] uname -a > uname: sysctl: Cannot allocate memory > > > Some programs are failing due this, like portmaster and chromium. > > This commit (r267961) has a lot of changes in the sysctl subsystem. > > Thanks! Hi folks, Sorry about the breakage. There appears to be some special case for read-only MIB SYSCTL strings which was ending up in an error code that's not so well documented. Sorry that it is not possible for me to test absolutely everything. Testing done from my side: - Several universe builds - Sysctl functionality has been verified and tested. I'm going to pull in the change again with the fix for "uname". If there are more problems popping up I need your help to test this patch. Thanks for your patience! --HPS