Unresponsive BMC after booting into Ubuntu

[Patrick Voelker]

Hm.  Sounds like a different issue. I don't think this solution will help me since I can't access the serial console.

> -----Original Message-----
> From: Andrei Kartashev [mailto:a.kartashev at yadro.com]
> Sent: Monday, November 23, 2020 9:18 PM
> To: Patrick Voelker; OpenBMC (openbmc at lists.ozlabs.org)
> Subject: Re: Unresponsive BMC after booting into Ubuntu
> 
> Hi,
> I had similar issue, but it was just "not loading some pages in webui
> and doesn't response on ipmi commands", ssh and serial console used to
> work. And yes, it appears after Linux boots on the host, but not with
> Windows.
> The root problem in my case was in PECI driver and power saving CPU
> modes.
> Here was the patch which solves the problem for me:
> https://patchwork.ozlabs.org/project/openbmc/patch/e6f4ab29854ac58a87
> 8189c1edece4e8eed2e7fd.camel at yadro.com/
> 
> I'm not sure if it is your problem also, if you use dbus-sensors you
> can check by stopping CPUsensor:
> 	systemctl stop xyz.openbmc_project.cpusensor.service
> If the problem gone after this, you got it =)
> 
> 
> On Mon, 2020-11-23 at 22:49 +0000, Patrick Voelker wrote:
> > I have a situation where, while booting the host into Ubuntu desktop
> > 18.04, my OpenBMC ast2500 BMC stops responding on all interfaces
> > including its debug serial console.  It doesn't do this when the host
> > boots into Windows.
> >
> > Nothing came up when I did an initial google search.  Also, nothing
> > unusual jumps out at me if I watch the BMC's 'journal -f' prior to
> > the issue.  No kernel panic or anything like that.
> >
> > Are there any known issues like this?  If not, are there some
> > pointers to relevant debug strategies for when BMC is not
> > available?  I'd like to avoid JTAG debugging the kernel if
> > possible.  :-)
> >
> --
> Best regards,
> Andrei Kartashev
>