From owner-freebsd-current@FreeBSD.ORG Fri Nov 18 17:00:47 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E924916A420; Fri, 18 Nov 2005 17:00:46 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 079A343E0D; Fri, 18 Nov 2005 16:59:19 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000030939.msg; Fri, 18 Nov 2005 22:58:59 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 128057, updated: 17.11.2005] To: Gleb Smirnoff References: <20051115101416.U68985@fledge.watson.org> <20051118114632.GY24212@cell.sick.ru> From: Victor Snezhko Date: Fri, 18 Nov 2005 22:58:55 +0600 In-Reply-To: <20051118114632.GY24212@cell.sick.ru> (Gleb Smirnoff's message of "Fri, 18 Nov 2005 14:46:32 +0300") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Fri, 18 Nov 2005 22:58:59 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-VVS-Spam: false Cc: freebsd-current@FreeBSD.org Subject: Re: pptpclient & CURRENT 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: Fri, 18 Nov 2005 17:00:47 -0000 Gleb Smirnoff writes: > A> Anyone successfully using pptpclient in CURRENT? > A> > A> Running CURRENT and ran 'pptpclient x.x.x.x LABEL' to setup my VPN > A> connection. On a CURRENT from Nov 8th, that rebooted my machine, but with > A> CURRENT, after an ifconfig or two (just viewing ifconfig output), i got: > A> > A> Unread portion of the kernel message buffer: > A> Memory modified after free 0xc3555aa0(28) val=0 @ 0xc3555aa0 > A> panic: Most recently used by in6_multi > > Looks like IPv6 is the problematic module. Yes, it was broken for some time (since Oct 21), but now the fix to the problem that caused many bugreports is committed by suz@ (he committed that on Wed Nov 15, before the bugreport we are discussing now). Minor problem remains with callout_stop being used everywhere. suz@ said he reviews the code now. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru