Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Sep 2021 09:04:44 -0400
From:      mike tancsa <mike@sentex.net>
To:        Alexander Motin <mav@FreeBSD.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: ipmi0: Watchdog set returned 0xc0 (releng_13)
Message-ID:  <48971f96-3bf1-6b66-ab15-af963f9c72b2@sentex.net>
In-Reply-To: <aa1213c1-8eee-507d-768d-6f0f3829e252@FreeBSD.org>
References:  <c065ff32-719f-ef2e-85b9-d5504a36810f@sentex.net> <51e58d7a-1b33-f7e3-13aa-3be5fee5c826@FreeBSD.org> <2c1ad9db-b92a-d0a8-b2ae-b3ffafc04604@sentex.net> <fc5f879f-91da-c45d-366c-29c721de948e@FreeBSD.org> <f93369e5-51b6-1a0c-cc14-e16a71be314b@sentex.net> <1f0d32e1-e907-080f-1669-65148c245dd8@sentex.net> <b6f97a7d-73ce-c3d3-ee56-5a7ae5bfed05@FreeBSD.org> <b5d6dbbc-92b8-52db-0aab-d2aa04288f8d@sentex.net> <586b04b4-d9b7-1597-4c8f-9bbcb9255c5a@sentex.net> <8fcb399d-8f26-b7a2-bf60-414d4ea1006e@FreeBSD.org> <b7324f74-f13e-4204-41f2-84fdc0882f79@sentex.net> <aa1213c1-8eee-507d-768d-6f0f3829e252@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 9/15/2021 7:19 PM, Alexander Motin wrote:
> ipmi0: Watchdog set returned 0xc0
>> ipmi0: Watchdog set returned 0xc0
>> ipmi0: Watchdog set returned 0xc0
>> ipmi0: Watchdog set returned 0xc0
>> ipmi0: Watchdog set returned 0xc0
>>
>> The initial attach looks as
>>
>> ipmi0: <IPMI System Interface> port 0xca2,0xca3 on acpi0
>> ipmi0: KCS mode found at io 0xca2 on acpi
>> ipmi0: IPMI device rev. 1, firmware rev. 1.73, version 2.0, device
>> support mask 0xbf
>> ipmi0: Number of channels 2
>> ipmi0: Attached watchdog
>> ipmi0: Establishing power cycle handler
> Status 0xc0 means "Node Busy. Command could not be processed because
> command processing resources are temporarily unavailable.".  Some
> sources propose command retrial after delay, but considering it is
> reported regularly I suppose it won't help.
>
> Have you tried to reset the BMC, for example with `ipmitool mc reset
> cold`, may be it unstuck that "Busy"?

Thanks, that seems to have fixed it in that I no longer see the 0xc0
message.  Its a production box so I dont want to test the dog.  But I
think I have another board in the back somewhere I can dig out and test with

    ---Mike





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48971f96-3bf1-6b66-ab15-af963f9c72b2>