From owner-freebsd-scsi@freebsd.org Thu Jun 1 15:29:43 2017 Return-Path: Delivered-To: freebsd-scsi@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 6CA23AFF77C for ; Thu, 1 Jun 2017 15:29:43 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D8517EB9F; Thu, 1 Jun 2017 15:29:42 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 32C0820951; Thu, 1 Jun 2017 11:29:36 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 01 Jun 2017 11:29:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=nAUAabkNLlWJDs/b8P 074zpUH5IOR6ZG7lySozCiOv4=; b=XgsFkafuvfNe2bidifKTbDcinE6QBLRHEa WMDMYGdcqUZsF2l3japnOAsl/O798sHghbwjniESk0E+Q2E4EDqOPdasTpixSgA2 ifylVparTUZrEoS7o0gUrUw1S/TAZkc6XR4cHt1J9hmNwC2a/uNucgkw42iT6xoO dlhcyqJdREHLJ1yiVbwwyoUkvFbzHKRPUxbVC9y5OKaI+5fdO7enK1vcIk0IfRUP R67JzWEL3Ad3FiLJZnGgO4gZbdK99oKHHytgBuex9vu+tQ7DEEqrwfAt+qesp7T5 9fRyLUQgvIU/aX8tf0r2Krc3cgMobgAlVxLP/FWvPCG7bEoiM7Sw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=nAUAabkNLlWJDs/b8P074zpUH5IOR6ZG7lySozCiOv4=; b=evyBP3qk aQ6We+I/kcxGWtWd22uLKBYMlDfN3kiGShEb/LVmEzfQf5Iq1ikRkbeVGqtkht8n 30Kc/Ccz4rziQ85+X2IHn0beQDQ6TAJWTzhF6jb7Bsxxudy/lQeg4H6stSXSeEUH d99TybJnxVAE04iaAeMeNzUK2uIsynNgNoafcQjlfkOmKJnIA9MmPUxvwpt/O2UJ 2SGjYhRrFroZqJ83XYH5S/w9Ce3Lk64dGR2rHzNI+fuyUdLVdibfYKmSO4Znqo2x OFcug4VU5kVhHSSGIC2gdMT//DWql/45TVRWcB+6eZqxft2Srrx1fimSJLHAv5Bx nPsIQqKi53ppaw== X-ME-Sender: X-Sasl-enc: u9/zicowU3Mb4KhPrP7LPTu5WTGSPijGYYvC5GN44fef 1496330975 Received: from [100.107.187.240] (52.sub-70-196-83.myvzw.com [70.196.83.52]) by mail.messagingengine.com (Postfix) with ESMTPA id D61522486C; Thu, 1 Jun 2017 11:29:35 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: mps(4) blocks panic-reboot From: Scott Long X-Mailer: iPhone Mail (14F89) In-Reply-To: Date: Thu, 1 Jun 2017 10:29:34 -0500 Cc: Harry Schmalzbauer , freebsd-scsi@freebsd.org, Scott Long Content-Transfer-Encoding: quoted-printable Message-Id: References: <592FDE8C.1090609@omnilan.de> To: Stephen Mcconnell X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 15:29:43 -0000 Good summary Steve, I forgot about this. I'm traveling today, but if I have= time tonight I'll see if I still have any notes or patches. Scott Sent from my iPhone > On Jun 1, 2017, at 10:25 AM, Stephen Mcconnell wrote: >=20 > I found a couple of emails between me and Scott a while back and we talked= > about this. The problem is that the SSU handling relies on interrupts, but= > interrupts stop due to the panic, so it hangs. Scott came up with a way > around it but we never decided on a final fix and then it was forgotten > about. If you have a way to reproduce this, I can try to find a fix here. > Or, I might be able to force the system to panic at the right time. >=20 > Steve >=20 >> -----Original Message----- >> From: Stephen Mcconnell [mailto:stephen.mcconnell@broadcom.com] >> Sent: Thursday, June 01, 2017 8:51 AM >> To: 'Harry Schmalzbauer'; 'freebsd-scsi@freebsd.org'; 'Scott Long' >> Subject: RE: mps(4) blocks panic-reboot >>=20 >> Scott, did you have a fix for this some time back? >>=20 >> Steve >>=20 >>> -----Original Message----- >>> From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd- >>> scsi@freebsd.org] On Behalf Of Harry Schmalzbauer >>> Sent: Thursday, June 01, 2017 3:30 AM >>> To: freebsd-scsi@freebsd.org >>> Subject: mps(4) blocks panic-reboot >>>=20 >>> Hello, >>>=20 >>> I'm not sure if scsi@ is the correct list, but since my problem seems >>> to be mps(4) related, I thought asking here shouldn't be too wrong. >>>=20 >>> There's not much to add to the topic: If my stable/11 setup panics, >>> the system doesn't reboot (besides IPMI-watchdog takes over this > task). >>> The machine stucks with these last lines: >>> Dumping 1669 out of 15734 >>> MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% >>> Dump complete >>> mps0: Sending StopUnit: path (xpt0:mps0:0:2:ffffffff): handle 12 >>> mps0: Incrementing SSU count >>> mps0: Sending StopUnit: path (xpt0:mps0:0:3:ffffffff): handle 11 >>> mps0: Incrementing SSU count >>> mps0: Sending StopUnit: path (xpt0:mps0:0:4:ffffffff): handle 10 >>> mps0: Incrementing SSU count >>> mps0: Sending StopUnit: path (xpt0:mps0:0:5:ffffffff): handle 9 >>> mps0: Incrementing SSU count >>> mps0: Sending StopUnit: path (xpt0:mps0:0:6:ffffffff): handle 13 >>> mps0: Incrementing SSU count >>>=20 >>> Then, nothing happens. On a similar setup without mps(4), the machine >>> reboots after the panic. >>>=20 >>> Is this a known problem/feature? >>>=20 >>> Thanks, >>>=20 >>> -harry >>> _______________________________________________ >>> freebsd-scsi@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-scsi >>> To unsubscribe, send any mail to > "freebsd-scsi-unsubscribe@freebsd.org"