From: Patrick Voelker <Patrick_Voelker@phoenix.com>
To: Andrei Kartashev <a.kartashev@yadro.com>,
Andrew Jeffery <andrew@aj.id.au>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: Unresponsive BMC after booting into Ubuntu
Date: Fri, 11 Dec 2020 01:13:54 +0000 [thread overview]
Message-ID: <d75be44a237e4de6ac94f6d84fc3935e@SCL-EXCHMB-13.phoenix.com> (raw)
In-Reply-To: <e9389df6-f4f5-4594-a803-b3b7598fb21e@www.fastmail.com>
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@ipmi_kcs3
systemctl stop phosphor-ipmi-kcs@ipmi_kcs4
systemctl stop phosphor-ipmi-net@eth0.socket
systemctl stop phosphor-ipmi-net@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@lists.ozlabs.org] On Behalf Of
> Andrew Jeffery
> Sent: Monday, November 30, 2020 4:47 PM
> To: openbmc@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
> to
> apply the change after the lockup occurred, but rather before. And then if
> you
> don't see lockups with the change applied, then it might be the same
> problem.
> It wasn't about recovering the BMC from the lockup context.
>
> But yeah, hopefully I'm not adding to the confusion here!
>
> Andrew
next prev parent reply other threads:[~2020-12-11 1:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 22:49 Unresponsive BMC after booting into Ubuntu Patrick Voelker
2020-11-24 5:17 ` Andrei Kartashev
2020-11-24 7:35 ` Patrick Voelker
2020-12-01 0:46 ` Andrew Jeffery
2020-12-11 1:13 ` Patrick Voelker [this message]
2020-12-11 15:29 ` Konstantin Klubnichkin
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=d75be44a237e4de6ac94f6d84fc3935e@SCL-EXCHMB-13.phoenix.com \
--to=patrick_voelker@phoenix.com \
--cc=a.kartashev@yadro.com \
--cc=andrew@aj.id.au \
--cc=openbmc@lists.ozlabs.org \
/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).