From owner-freebsd-stable@FreeBSD.ORG Mon Aug 27 09:39:15 2012 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 A8617106564A for ; Mon, 27 Aug 2012 09:39:15 +0000 (UTC) (envelope-from orientalsensation@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6AB2D8FC19 for ; Mon, 27 Aug 2012 09:39:15 +0000 (UTC) Received: by ialo14 with SMTP id o14so9792664ial.13 for ; Mon, 27 Aug 2012 02:39:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=G6z94U0b5hvIm9JD6RO4rcY3pbkGHZp3IsP6IaTF7Hk=; b=XtTSn7IfR/niJrnAzlJD+l6Gxolilv9+4e8uLdMtVtHRAfwI+5riV2+ruC8Rr9jB3r kdGyaGZjQwk7vkb0p4RypsZKr+yB3ZilttwrixSiMfC8mNn02gmcyKX/o98A37Vg4lOa M4wVKXLHqREwQ7++IHRqJ19TNsSkjIypY/nL+HV+Ayk1fqG+MlR8xQ13lfDPyWJ/97xE 1NnOKqikfqppKgb3nmZc+n2JqbGOo1nl+FRA6XRAQipIM5BEaULRErzDPgbWOpUqM5F1 vNQU9ze7E0m2YHpB/Yq9YKlCWeSOT3lOdSQS8D8bcLfo16g0Ns0ekz/8tMl9OOvLb8De mYAw== MIME-Version: 1.0 Received: by 10.50.213.97 with SMTP id nr1mr9562832igc.40.1346060354708; Mon, 27 Aug 2012 02:39:14 -0700 (PDT) Sender: orientalsensation@gmail.com Received: by 10.64.81.226 with HTTP; Mon, 27 Aug 2012 02:39:14 -0700 (PDT) In-Reply-To: <86d32czo3s.fsf@ds4.des.no> References: <86d32czo3s.fsf@ds4.des.no> Date: Mon, 27 Aug 2012 11:39:14 +0200 X-Google-Sender-Auth: t-Jqb--qsYT9NzcCXYdK4dXvXWc Message-ID: From: OriS To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= Subject: Re: Weird message in dmesg 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: Mon, 27 Aug 2012 09:39:15 -0000 Yep, this also causes the warning not to be emitted at all. Well, maybe it'd be a good idea to set it to 0 on amd64 systems for amd64-RELEASE's. OriS On Mon, Aug 27, 2012 at 11:21 AM, Dag-Erling Sm=C3=B8rgrav wro= te: > OriS writes: > > The value of kern.maxswzone in /boot/loader.conf is: > > > > kern.maxswzone=3D201326592 > > On an amd64 system, you should just set it to 0. > > DES > -- > Dag-Erling Sm=C3=B8rgrav - des@des.no >