From owner-freebsd-current@freebsd.org  Tue Aug 21 14:19:31 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 898B510740B5
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue, 21 Aug 2018 14:19:31 +0000 (UTC) (envelope-from zec@fer.hr)
Received: from mail.fer.hr (mail.fer.hr [161.53.72.233])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
 (Client CN "mail.fer.hr", Issuer "TERENA SSL CA 3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id F130585C3A;
 Tue, 21 Aug 2018 14:19:30 +0000 (UTC) (envelope-from zec@fer.hr)
Received: from x23 (31.147.25.88) by MAIL.fer.hr (161.53.72.233) with
 Microsoft SMTP Server (TLS) id 14.3.399.0; Tue, 21 Aug 2018 16:19:25 +0200
Date: Tue, 21 Aug 2018 16:20:51 +0200
From: Marko Zec <zec@fer.hr>
To: Olivier =?ISO-8859-1?Q?Cochard-Labb=E9?= <olivier@freebsd.org>
CC: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, freebsd-current
 <freebsd-current@freebsd.org>
Subject: Re: Loading carp module crash i386 (12-ALPHA2), seems VNET related
Message-ID: <20180821162051.4fd0f1eb@x23>
In-Reply-To: <D948BD06-D627-4D9B-BFDA-AA1D077ECEFB@lists.zabbadoz.net>
References: <CA+q+TcqN-YAXKQuZPQcrjmgABJJ22Pm+9-B9+Z8LH==0o+g2BA@mail.gmail.com>
 <20180821113051.7d35bc39@x23>
 <CA+q+Tcr=LXEQ1tzgycY5hhJ6X5CKvu2QgW1J-rvoGjsXyD=L8A@mail.gmail.com>
 <D948BD06-D627-4D9B-BFDA-AA1D077ECEFB@lists.zabbadoz.net>
X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="MP_/4Myh3kMKzIkherxz0vVdmsw"
X-Originating-IP: [31.147.25.88]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2018 14:19:31 -0000

--MP_/4Myh3kMKzIkherxz0vVdmsw
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Tue, 21 Aug 2018 13:15:04 +0000
"Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> wrote:
...
>  From the backtrace it seems like VNET_PCPUSTAT_SYSINIT() or the
> kernel linker, or possible pcpu things.  People have recently been
> touching almost all of this :(
> 
> Do you have a last-good revision?

Perhaps the PCPU area is overflowing?  Maybe increasing the
UMA_PCPU_ALLOC_SIZE could make the panic go away (this by no means
should be considered a proper fix)?

Marko

--MP_/4Myh3kMKzIkherxz0vVdmsw
Content-Type: text/x-patch
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="pcpu_overflow_hunch.diff"

Index: sys/sys/pcpu.h
===================================================================
--- sys/sys/pcpu.h	(revision 338128)
+++ sys/sys/pcpu.h	(working copy)
@@ -219,7 +219,7 @@
 #endif
 #define	curvidata	PCPU_GET(vidata)
 
-#define UMA_PCPU_ALLOC_SIZE		PAGE_SIZE
+#define UMA_PCPU_ALLOC_SIZE		(PAGE_SIZE * 16)
 
 #ifdef CTASSERT
 #if defined(__i386__) || defined(__amd64__)

--MP_/4Myh3kMKzIkherxz0vVdmsw--