From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Joel Stanley <joel@jms.id.au>,
Jae Hyun Yoo <jae.hyun.yoo@intel.com>,
Rob Herring <robh+dt@kernel.org>, Corey Minyard <minyard@acm.org>,
Andrew Jeffery <andrew@aj.id.au>, Cedric Le Goater <clg@kaod.org>,
Haiyue Wang <haiyue.wang@linux.intel.com>,
devicetree <devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-aspeed <linux-aspeed@lists.ozlabs.org>,
openipmi-developer@lists.sourceforge.net
Subject: Re: [PATCH -next 0/4] Add LCLK control into Aspeed LPC sub drivers
Date: Thu, 4 Nov 2021 09:09:41 -0700 [thread overview]
Message-ID: <f9203632-4730-dba6-49a7-240b45a00bed@linux.intel.com> (raw)
In-Reply-To: <YYM78OxYMYwiFzWD@hatter.bewilderbeest.net>
On 11/3/2021 6:48 PM, Zev Weiss wrote:
> On Wed, Nov 03, 2021 at 08:56:10AM PDT, Jae Hyun Yoo wrote:
>>
>> Hi Zev,
>>
>> Not sure but looks like one of LPC functions is enabled while kernel
>> booting.
>
> Looks like that was exactly the clue I needed -- obvious in retrospect,
> but I realize now that I'm only seeing this happen when I bypass the
> normal shutdown sequence via 'reboot -f'; with a plain 'reboot' I don't
> hit any problems. Can you reproduce it that way?
My system doesn't follow the reproduction pattern. What I usually do to
reproduce it is, making a host reset and followed by making a BMC reset
then host will try to send something through KCS channel and snoop-80
while BMC LPC drivers are being loaded. It's not easy to reproduce it
using my system and it's very timing sensitive.
As I suggested in previous email, disable all LPC sub functions and
enable back one by one. It could help for identifying which LPC sub
module causes the issue.
-Jae
next prev parent reply other threads:[~2021-11-04 16:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 23:37 [PATCH -next 0/4] Add LCLK control into Aspeed LPC sub drivers jae.hyun.yoo
2021-11-01 23:36 ` Joel Stanley
2021-11-02 12:22 ` Corey Minyard
2021-11-02 16:38 ` Jae Hyun Yoo
2021-11-03 0:04 ` Zev Weiss
2021-11-03 0:17 ` Jae Hyun Yoo
2021-11-03 0:30 ` Zev Weiss
2021-11-03 0:54 ` Jae Hyun Yoo
2021-11-03 1:09 ` Zev Weiss
2021-11-03 15:56 ` Jae Hyun Yoo
2021-11-04 1:48 ` Zev Weiss
2021-11-04 16:09 ` Jae Hyun Yoo [this message]
2021-11-01 23:37 ` [PATCH -next 1/4] ARM: dts: aspeed: add LCLK setting into LPC IBT node jae.hyun.yoo
2021-11-01 23:33 ` Joel Stanley
2021-11-01 23:48 ` Jae Hyun Yoo
2021-11-01 23:52 ` Joel Stanley
2021-11-01 23:59 ` Jae Hyun Yoo
2021-11-02 22:21 ` Andrew Jeffery
2021-11-01 23:37 ` [PATCH -next 2/4] ipmi: bt: add clock control logic jae.hyun.yoo
2021-11-01 23:32 ` Joel Stanley
2021-11-02 9:35 ` Cédric Le Goater
2021-11-02 16:36 ` Jae Hyun Yoo
2021-11-02 22:14 ` Andrew Jeffery
2021-11-01 23:37 ` [PATCH -next 3/4] ARM: dts: aspeed: add LCLK setting into LPC KCS nodes jae.hyun.yoo
2021-11-01 23:34 ` Joel Stanley
2021-11-02 22:22 ` Andrew Jeffery
2021-11-03 16:15 ` Jae Hyun Yoo
2021-11-01 23:37 ` [PATCH -next 4/4] ipmi: kcs_bmc_aspeed: add clock control logic jae.hyun.yoo
2021-11-01 23:33 ` Joel Stanley
2021-11-02 3:15 ` ChiaWei Wang
2021-11-02 3:28 ` Joel Stanley
2021-11-02 16:35 ` Jae Hyun Yoo
2021-11-03 1:55 ` ChiaWei Wang
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=f9203632-4730-dba6-49a7-240b45a00bed@linux.intel.com \
--to=jae.hyun.yoo@linux.intel.com \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=devicetree@vger.kernel.org \
--cc=haiyue.wang@linux.intel.com \
--cc=jae.hyun.yoo@intel.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=robh+dt@kernel.org \
--cc=zev@bewilderbeest.net \
/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;
as well as URLs for NNTP newsgroup(s).