All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Feist <james.feist@linux.intel.com>
To: Milton Miller II <miltonm@us.ibm.com>
Cc: Andrew Jeffery <andrew@aj.id.au>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Ryan Chen <ryan_chen@aspeedtech.com>
Subject: Re: phosphor-isolation
Date: Fri, 20 Sep 2019 11:16:38 -0700	[thread overview]
Message-ID: <dd3f64aa-e053-6c33-bf3e-fa6031eafb57@linux.intel.com> (raw)
In-Reply-To: <OFB4439398.C2024144-ON0025847B.0059AC2A-0025847B.0059BE4A@notes.na.collabserv.com>

On 9/20/19 9:20 AM, Milton Miller II wrote:
> On September 20, 2019, around 10:56AM in some timezone, James Feist wrote:
>> On 9/19/19 8:47 PM, Andrew Jeffery wrote:
>>> On Fri, 20 Sep 2019, at 03:03, James Feist wrote:
>>>> I enabled phosphor-isolation on my system and noticed that kcs no
>>>> longer
>>>> worked afterwards. Commenting out this section:
>>>>
>>>>
> 
>>>>
>>>> +	/* iLPC2AHB */
>>>> +	val = readl(AST_SCU_BASE + AST_SCU_HW_STRAP1);
>>>> +	val |= SCU_HW_STRAP_LPC_DEC_SUPER_IO;
>>>> +	writel(val, AST_SCU_BASE + AST_SCU_HW_STRAP1);
>>>>
>>>>
>>>> Seems to make KCS work again.
> 
> That configuration is disabling superio decoding, which means the host
> will no longer be able to configure the superio hardware on the LPC bus.
> 
>>>
>>> That is an unexpected result. Have you asked ASPEED about it? I've
>>> added
>>> Ryan to Cc. I must admit I didn't test the patch with systems that
>>> use KCS
>>> because OpenPOWER exclusively uses BT for IPMI (though we're
>>> starting
>>> to exploit the KCS interfaces for an LPC MCTP binding).
>>>
>>> Having said that, the systems that we're testing our LPC MCTP
>>> binding on
>>> would have this patch applied, so presumably we're not seeing the
>>> same
>>> effect there. They're 2500-based systems, is that what you're
>>> testing with?
>>
>> Yes I am.
>>
> 
> As an outside observer without hardware, can you check:
> 
> (1) Did you check from the OS or just from a BIOS inventory?

Attempting to send ipmi commands from uefi/linux stopped working. Linux 
driver on host reported issues communicating to bmc.

> 
> (2) Is there code to enable the KCS peripheral from the bmc

There is a driver and kcsbridged.
> 
> (3) Will the host try to use the KCS even though it can
>      not find the superio to choose the port and interrupt?

Yes.

> 
> 
> 
> 
> 
>>>>
>>>> Do we need this part set? If so, should we
>>>> create a phosphor-isolation-kcs and phosphor-isolation-bt?
>>>
>>> I hope not, given that leaving the SuperIO decoding enable allows
>> the
>>> host to (slowly) scrape BMC memory (or if iLPC2AHB writes are
>>> allowed,
>>> open faster backdoors). We should root-cause the issue before
>>> exploring this path.
>>>
>>> Andrew
> 

  reply	other threads:[~2019-09-20 18:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 17:33 phosphor-isolation James Feist
2019-09-20  3:47 ` phosphor-isolation Andrew Jeffery
2019-09-20 15:55   ` phosphor-isolation James Feist
2019-09-20 16:20   ` phosphor-isolation Milton Miller II
2019-09-20 18:16     ` James Feist [this message]
2019-09-21  0:34       ` phosphor-isolation Ryan Chen
2019-09-20 19:51     ` phosphor-isolation Milton Miller II

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=dd3f64aa-e053-6c33-bf3e-fa6031eafb57@linux.intel.com \
    --to=james.feist@linux.intel.com \
    --cc=andrew@aj.id.au \
    --cc=miltonm@us.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ryan_chen@aspeedtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.