From owner-freebsd-current@FreeBSD.ORG Wed Jan 11 00:07:10 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBDC0106566B; Wed, 11 Jan 2012 00:07:10 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 935B48FC08; Wed, 11 Jan 2012 00:07:10 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so172074vcb.13 for ; Tue, 10 Jan 2012 16:07:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=yMH3T0nJojN4Y7h7GWAPhdBB7B/X7WcNAlcEeKxchqI=; b=IC276RFkeNiEepSmGUQljHy9KksTLdgPPBjE49Zn84UGT1LOOX1hvI97TJdjufPetn xsapclDRW6y7iMth87QLxhrTYhKAGYE1jIHtxEKuPkCREQPCH3t60XpNKcLZCeKl0QW4 RnP3EgAX+aGjJ2P6yO8rUZ2hT8qdEhMABCwXw= MIME-Version: 1.0 Received: by 10.52.24.35 with SMTP id r3mr10453773vdf.81.1326240429775; Tue, 10 Jan 2012 16:07:09 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Tue, 10 Jan 2012 16:07:09 -0800 (PST) In-Reply-To: <1791250845.20120111030529@serebryakov.spb.ru> References: <1791250845.20120111030529@serebryakov.spb.ru> Date: Tue, 10 Jan 2012 16:07:09 -0800 X-Google-Sender-Auth: aoUZAh9Wcuavz9YFe1Mz5nBLeOU Message-ID: From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD current Subject: Re: Very fresh (two days ago) 10-current becomes completely unresponsive under load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 11 Jan 2012 00:07:11 -0000 Hi, I'd suggest verifying that it's _just_ a kernel update that messes with it. And once you've verified that, what about doing some kernel source version bisecting to narrow down when the relevant change went in that's caused your regression? Adrian