From owner-freebsd-current@freebsd.org Thu Aug 20 22:15:09 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E75E9BE5C6; Thu, 20 Aug 2015 22:15:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E2779BB3; Thu, 20 Aug 2015 22:15:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igxp17 with SMTP id p17so1709222igx.1; Thu, 20 Aug 2015 15:15:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=Il7S7eqt94dWYuTGW/z/8qoN8ZQszbjZaY1Np8xirhM=; b=B9sqlhRTtHhFWrHx6kLmvpKCXWolVf1T8h7slnmBSRVtRkTnpzjVz12ZaPqtnZlYPn YeNuiI+RvAGGN2mdQIRr2r4K/rYHi1YeRYe0DeLBw7O1xf2ClTbpV+jxqhgeS7xvc8P8 v4M3R5OUDYwET1IhfiPLMzIroQnlHFoBTIXR+myYL/Tfwl7GrV6oHxyWQohbRUc/jCVb LtKwGXWaScRAG4iniVwK++FfX+ZO/oB6uEgBEYwV1/1euBYiBJAbXgwO+M4hUqzvEmQv ZpoanVGeZb3S2sAU3pBwRRVHtfCEsyPl4Ef7M6al6CebIN3k/dc2ck5x6JpRnZMIAA9y 61hA== MIME-Version: 1.0 X-Received: by 10.50.28.70 with SMTP id z6mr275073igg.61.1440108908297; Thu, 20 Aug 2015 15:15:08 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.38.133 with HTTP; Thu, 20 Aug 2015 15:15:08 -0700 (PDT) Date: Thu, 20 Aug 2015 15:15:08 -0700 X-Google-Sender-Auth: zKga-ms6LMw5DejYcOr_EiFXwIo Message-ID: Subject: freebsd-head: suddenly NMI panics lead to ddb being unable to stop CPUs? From: Adrian Chadd To: "freebsd-arch@freebsd.org" , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Thu, 20 Aug 2015 22:15:09 -0000 Hi! This has started happening on -HEAD recently. No, I don't have any more details yet than "recently." Whenever I get an NMI panic (and getting an NMI is a separate issue, sigh) I get a slew of "failed to stop cpu" messages, and all CPUs enter ddb. This is .. sub-optimal. Has anyone seen this? Does anyone have any ideas? -adrian