From owner-freebsd-net@FreeBSD.ORG Sat Apr 9 02:31:30 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id ADDB1106566C for ; Sat, 9 Apr 2011 02:31:30 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 553C1161154; Sat, 9 Apr 2011 02:30:40 +0000 (UTC) Message-ID: <4D9FC4CF.9090704@FreeBSD.org> Date: Fri, 08 Apr 2011 19:30:39 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <4D9FAC18.1070202@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org Subject: Re: in6.c and panic: 0xc63dd000 must be migratable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Apr 2011 02:31:30 -0000 On 04/08/2011 17:57, Bjoern A. Zeeb wrote: > On Fri, 8 Apr 2011, Doug Barton wrote: > >> Bjoern, >> >> We're seeing something very similar to the following with pf and IPv6: > > similar to what? We're seeing the "must be migratable" part of the panic, but nothing else. > It would be helpful to include more data in your problem reports. > > What freebsd release? Yeah, sorry, not my best effort, but we were in the middle of a crisis. :) This is 8-stable (post 8.2-RELEASE) i386. > Can you reproduce it? If so, how? Not at will, but it's happened twice now. >> panic: 0xc63dd000 must be migratable >> cpuid = 1 >> panic: 0xc63dd000 must be migratable >> cpuid = 1 >> panic: 0xc63dd000 must be migratable >> cpuid = 1 >> panic: 0xc63dd000 must be migratable >> cpuid = 1 >> panic: 0xc63dd000 must be migratable >> cpuid = 1 >> panic: 0xc63dd000 must be migratable >> cpuid = 1 >> panic: 0xc63dd000 must be migratable >> cpuid = 1 This is the bit we see. Breaking to the debugger hasn't worked, and dumping is not an option (I inherited this system, trying to get it tuned up now). > Depsite being in the subject that's just follow-up problems, though > thinking about it (very wild guess) -- how many cores do you have and are you > running with flowtable enabled? It's an SMP system, and yes, FLOWTABLE was in the kernel config. I took that out, and got the KDB options sorted out so that if it happens again hopefully I can get a stack trace. Thanks for the FLOWTABLE suggestion, wish I'd remembered that one myself. :) Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/