From owner-freebsd-current@FreeBSD.ORG Wed Nov 27 10:49:20 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B54775EB for ; Wed, 27 Nov 2013 10:49:20 +0000 (UTC) Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 99B0127BC for ; Wed, 27 Nov 2013 10:49:20 +0000 (UTC) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id rARAnCum040847; Wed, 27 Nov 2013 02:49:16 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <201311271049.rARAnCum040847@gw.catspoiler.org> Date: Wed, 27 Nov 2013 02:49:12 -0800 (PST) From: Don Lewis Subject: Re: panic: double fault with 11.0-CURRENT r258504 To: kostikbel@gmail.com In-Reply-To: <201311271041.rARAfUP2040781@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.16 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, 27 Nov 2013 10:49:20 -0000 On 27 Nov, I wrote: > On 27 Nov, Konstantin Belousov wrote: >> On Wed, Nov 27, 2013 at 01:13:41AM -0800, Don Lewis wrote: >>> On 27 Nov, Konstantin Belousov wrote: >>> > On Wed, Nov 27, 2013 at 12:22:27AM -0800, Don Lewis wrote: >>> >> It took a while, but I just got another double fault, though this one is >>> >> somewhat different. This time it trapped in cpu_switch(), which >>> >> resulted in calls to >>> >> trap()->printf()->...->putchar()->msgbuf_addstr()->_mtx_lock_spin_flags() >>> >> where it trapped again. >>> >> >>> >> Sitting at DDB prompt ... >>> > >>> > Does 'show allpcpu' work ? >>> >>> Yup. For both CPUs, curthread == idlethread, both CPUs have the same >>> curpcb. What is "dynamic pcpu"? The values differ considerably between >>> the two CPUs. >> >> Are you sure about curpcb being the same for two CPUs ? This is rather >> broken. The best would be to show the actual ddb output. > > It turns out that they are different: > 0xe4f62d60 > 0xe4f65d60 > > Screenshot here: And screenshot of the stack trace here: