From owner-freebsd-stable@FreeBSD.ORG Mon Aug 11 22:32:07 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 369768C1 for ; Mon, 11 Aug 2014 22:32:07 +0000 (UTC) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E4D362E0F for ; Mon, 11 Aug 2014 22:32:06 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.7/8.14.7) with ESMTP id s7BMW4XL040569; Mon, 11 Aug 2014 18:32:04 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.7/8.14.4/Submit) id s7BMW22I040568; Mon, 11 Aug 2014 18:32:02 -0400 (EDT) (envelope-from wollman) Date: Mon, 11 Aug 2014 18:32:02 -0400 (EDT) From: Garrett Wollman Message-Id: <201408112232.s7BMW22I040568@hergotha.csail.mit.edu> To: bengta@sics.se Subject: Re: 9.3-RELEASE still instapanics on multi-mps(4) servers X-Newsgroups: mit.lcs.mail.freebsd-stable In-Reply-To: References: Organization: none X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (hergotha.csail.mit.edu [127.0.0.1]); Mon, 11 Aug 2014 18:32:04 -0400 (EDT) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on hergotha.csail.mit.edu Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2014 22:32:07 -0000 In article you write: >I have a dual-mps (one Dell H200 and one LSI 9207) system now running >9.1 (w patched sys/kern/kern_intr.c) that I intend to upgrade to 9.3 >shortly. Is it enough to boot a 9.3 memstick to provoke the issue? Yes, it was sufficient on both of the machines that have this problem for me. But two mps controllers might not be enough -- the machines that fail for me all have three. I have a patch (with debugging printfs, not a fix) that I haven't had time to try yet, but should be able to do that tomorrow. -GAWollman