mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Andrew Banman <abanman@hpe.com>, Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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
Date: Wed, 22 Aug 2018 11:14:52 -0500	[thread overview]
Message-ID: <a72a169e-ce1b-500c-7910-b400c7842033@acm.org> (raw)
In-Reply-To: <20180821221443.hhgcnzw6xttaih3i@linux-tqvx.americas.hpqcorp.net>

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?

BTW, you can use the "hotmod" capability of the IPMI driver to add the 
device
dynamically.

-corey

  reply	other threads:[~2018-08-22 16:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 22:14 Andrew Banman
2018-08-22 16:14 ` Corey Minyard [this message]
2018-08-22 16:23   ` Andrew Banman
2018-08-23 16:22     ` Corey Minyard
2018-08-23 16:52       ` Andrew Banman
2018-08-23 19:06         ` Corey Minyard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a72a169e-ce1b-500c-7910-b400c7842033@acm.org \
    --to=minyard@acm.org \
    --cc=abanman@hpe.com \
    --cc=arnd@arndb.de \
    --cc=frank.ramsay@hpe.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=justin.ernst@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    --cc=rja@hpe.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®