From owner-freebsd-current@FreeBSD.ORG Wed Jun 19 12:20:28 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B1F42BDD for ; Wed, 19 Jun 2013 12:20:28 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 2A25C1D17 for ; Wed, 19 Jun 2013 12:20:27 +0000 (UTC) Received: (qmail 58617 invoked from network); 19 Jun 2013 13:15:02 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 19 Jun 2013 13:15:02 -0000 Message-ID: <51C1A1FE.8040300@freebsd.org> Date: Wed, 19 Jun 2013 14:20:14 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Ian FREISLICH Subject: Re: Panic in tcp_input References: <51C17A3B.2030809@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: jeffr@FreeBSD.org, glebius@FreeBSD.org, current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 19 Jun 2013 12:20:28 -0000 On 19.06.2013 11:34, Ian FREISLICH wrote: > Andre Oppermann wrote: >> On 19.06.2013 11:10, Ian FREISLICH wrote: >>> Hi >>> >>> I'm seeing this panic quite regularly now. Most recent sighting on r251858. >> >> This panic message is not very informative and very hard to extract any >> meaningful hints. Do you have a core dump and matching debug kernel? > > I do. If you can send me your public ssh key in private email, I > can give you access to the server in question. It bombs while accessing a per-cpu counter: (kgdb) frame 11 #11 0xffffffff8054518e in tcp_input (m=, off0=Cannot access memory at address 0x14) at counter.h:45 45 __asm __volatile("addq\t%1,%%gs:(%0)" This seems to be a fallout of the recent UMA changes and its interaction with the per-cpu counter(9) system. Adding in and handing over to Gleb and Jeff as they touched this area last. -- Andre