From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jae Hyun Yoo Date: Thu, 4 Nov 2021 09:09:41 -0700 Subject: [PATCH -next 0/4] Add LCLK control into Aspeed LPC sub drivers In-Reply-To: References: <20211101233751.49222-1-jae.hyun.yoo@intel.com> <63678f47-8b4a-1385-a755-bc7c2316ca0d@linux.intel.com> <768252cc-2466-3b4b-9087-549b83e00a81@linux.intel.com> Message-ID: List-Id: To: linux-aspeed@lists.ozlabs.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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