Unresponsive BMC after booting into Ubuntu
Patrick_Voelker at phoenix.com
Fri Dec 11 12:13:54 AEDT 2020
I gave disabling the cpusensor service a try and it didn't make a difference. The BMC still goes out to lunch. Thanks for the suggestion.
I tried disabling all the IPMI handlers but that didn't seem to help either:
systemctl stop phosphor-ipmi-kcs at ipmi_kcs3
systemctl stop phosphor-ipmi-kcs at ipmi_kcs4
systemctl stop phosphor-ipmi-net at eth0.socket
systemctl stop phosphor-ipmi-net at eth1.socket
systemctl stop phosphor-ipmi-host
I think my next step will be to try disabling kernel config options that are related to things that can be influenced by the host.
> -----Original Message-----
> From: openbmc [mailto:openbmc-
> bounces+patrick_voelker=phoenix.com at lists.ozlabs.org] On Behalf Of
> Andrew Jeffery
> Sent: Monday, November 30, 2020 4:47 PM
> To: openbmc at lists.ozlabs.org
> Subject: Re: Unresponsive BMC after booting into Ubuntu
> On Tue, 24 Nov 2020, at 18:05, Patrick Voelker wrote:
> > Hm. Sounds like a different issue. I don't think this solution will
> > help me since I can't access the serial console.
> I'm not Andrei, but my understanding was that he wasn't suggesting you try
> apply the change after the lockup occurred, but rather before. And then if
> don't see lockups with the change applied, then it might be the same
> It wasn't about recovering the BMC from the lockup context.
> But yeah, hopefully I'm not adding to the confusion here!
More information about the openbmc