Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp618334imm; Wed, 22 Aug 2018 09:39:21 -0700 (PDT) X-Google-Smtp-Source: AA+uWPwdyAKeqZFseijIuF08z+BFZzNhCM9b1DgylFc6ChdJtWZfsIwd3sRBDYINYceRmIHS054J X-Received: by 2002:a17:902:e3:: with SMTP id a90-v6mr30954375pla.227.1534955961544; Wed, 22 Aug 2018 09:39:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534955961; cv=none; d=google.com; s=arc-20160816; b=pCwVm059N2CWj6CPLkjdqVdre9HIwShVi636ymKs89l6hyRVSJVfz2rzol5qO5aMDA ShdazUnDK139iC+ui/H3vQ6hDLa/1bBsgiz3rGqWHBKeDbR0HF2HHxGxTjaHhjYAOsGt 6iB53FuCH/+NTRbc58EGMGaboFcv0R1cIVWdMOn/w/aXpHhO/voTJ2bcR9GcIzmk8GYQ opGVDkH7+Ht4EWJXo1UuaLYoN6+LTSH3TtIjYCnmAc0aBZuVrbU4tnGl8Y6vwkrdIxen qBrHNCmg1PAQhjxyAxf3h8TKyT6Xwd2A92wB7J4aobysXvsXmS+lb/ktiteADlBIgZhu bFZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=z4whY6CINOZrevUhny0L5TBoHmgzE7BMwr6FEogsJ5k=; b=jqSLFVK9T35O1LRIqO4OwxQAphDlfrwJEGOIq9lPf88q2o2gio9T0Bk4vGK3F/lB/K eRia0Cdm8gKSbcMobb/GMiM4FOFkWnxRh5fjzYHE2WKWS4lXKK18ZPWan2Ea4FSp1y98 T6fipgmRpeQKJtbat0xkXEvVts6Fq+uQbvXmNf0XzOaYcxG0LvfiBHwxnFQCp1kTG8u8 Ef+/tDFxfpc59BJV9yCXbEfz98cAhD2TH/XgK1KW35XfZBoRXIzsJ9zYRqrEP2J0ZFKy MZLI919qdExR4xOvaCCU3LxDTeAhlImgbAg3hMXYmO8w60ug0Vfp9cGvSBgDaKxLgQp7 S3BQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s61-v6si1893670plb.125.2018.08.22.09.39.05; Wed, 22 Aug 2018 09:39:21 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726896AbeHVTt3 (ORCPT + 99 others); Wed, 22 Aug 2018 15:49:29 -0400 Received: from g2t2352.austin.hpe.com ([15.233.44.25]:37025 "EHLO g2t2352.austin.hpe.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726550AbeHVTt3 (ORCPT ); Wed, 22 Aug 2018 15:49:29 -0400 X-Greylist: delayed 65563 seconds by postgrey-1.27 at vger.kernel.org; Wed, 22 Aug 2018 15:49:29 EDT Received: from g2t2360.austin.hpecorp.net (g2t2360.austin.hpecorp.net [16.196.225.135]) by g2t2352.austin.hpe.com (Postfix) with ESMTP id D4A82A1; Wed, 22 Aug 2018 16:23:56 +0000 (UTC) Received: from linux-tqvx (linux-tqvx.americas.hpqcorp.net [10.34.51.15]) by g2t2360.austin.hpecorp.net (Postfix) with ESMTP id 4B39137; Wed, 22 Aug 2018 16:23:56 +0000 (UTC) Date: Wed, 22 Aug 2018 11:23:54 -0500 From: Andrew Banman To: Corey Minyard Cc: Andrew Banman , Arnd Bergmann , Greg Kroah-Hartman , justin.ernst@hpe.com, rja@hpe.com, frank.ramsay@hpe.com, openipmi-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org Subject: Re: [RFC] IPMI state machine regression Message-ID: <20180822162352.q7qc2udqabbqxdya@linux-tqvx> References: <20180821221443.hhgcnzw6xttaih3i@linux-tqvx.americas.hpqcorp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170912 (1.9.0) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 22, 2018 at 11:14:52AM -0500, Corey Minyard wrote: > On 08/21/2018 05:14 PM, Andrew Banman wrote: > > Dear IPMI supporters, > > > > We observe a window in IPMI BT's opportunistic get capabilities request, > > wherein GET_DEVICE_GUID and GET_DEVICE_ID requests may start while the BT state > > machine is in WR_CONSUME. Following this, the 0xD5 error code is forced in > > bt_start_transaction, IPMI fails to initialize, and the interface is torn down. > > There is no mechanism to retry bringing up the interface in open() /dev/ipmi. > > This leaves IPMI hosed until you reload modules. Looks to happen after we call > > schedule(). > > When was the latest kernel where this worked properly?? Also, what hardware > is this? This is UV4. First known bad commit, but I am not sure if the timing issue predates it: commit aa9c9ab2443e3b9562c6c7cfc245a9e43b557d14 Author: Jeremy Kerr Date: Fri Aug 25 15:47:24 2017 +0800 ipmi: allow dynamic BMC version information Hits less frequently with older kernels so I didn't see it until recently when it became more frequent. > > BTW, you can use the "hotmod" capability of the IPMI driver to add the > device > dynamically. > > -corey