Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Sep 2021 21:29:59 -0400
From:      Alexander Motin <mav@FreeBSD.org>
To:        mike tancsa <mike@sentex.net>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: ipmi0: Watchdog set returned 0xc0 (releng_13)
Message-ID:  <b6f97a7d-73ce-c3d3-ee56-5a7ae5bfed05@FreeBSD.org>
In-Reply-To: <1f0d32e1-e907-080f-1669-65148c245dd8@sentex.net>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mike,

Could you try my 6c2d4404161a commit?  I don't know about your case, but
it fixes 0xcc error I see on my systems for timeouts below 120 seconds.

On 17.08.2021 15:31, mike tancsa wrote:
> Actually, even stranger now, I updated the base src and am no longer
> able to reboot via watchdog
> 
> Instead, dmesg has this pop up
> 
> 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
> 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
> interrupt                   total
> irq4: uart0                            4
> cpu0:timer                          5726
> cpu1:timer                          4694
> cpu2:timer                          6007
> cpu3:timer                          4449
> irq42: xhci0                         347
> irq43: ahci0                        6448
> irq44: igb0:rxq0                     133
> irq45: igb0:rxq1                    1825
> irq46: igb0:rxq2                       5
> irq47: igb0:rxq3                       4
> irq48: igb0:aq                         2
> Total                       29644
> KDB: stack backtrace:
> #0 0xffffffff80c6ad65 at kdb_backtrace+0x65
> #1 0xffffffff80baf74d at hardclock+0x1bd
> #2 0xffffffff80bb07c4 at handleevents+0xb4
> #3 0xffffffff80bb152e at timercb+0x24e
> #4 0xffffffff81165efb at lapic_handle_timer+0x9b
> #5 0xffffffff8107e7c1 at Xtimerint+0xb1
> #6 0xffffffff81068f0e at cpu_idle_acpi+0x3e
> #7 0xffffffff81068fbf at cpu_idle+0x9f
> #8 0xffffffff80c52864 at sched_idletd+0x2e4
> #9 0xffffffff80bdafce at fork_exit+0x7e
> #10 0xffffffff8107dafe at fork_trampoline+0xe
> 
> A kernel from Jul 22 does indeed work. Looking at the sel info I am able
> to reboot it with a killall  -9 watchdogd.
> 
> root@r13aug21:/boot # ipmitool sel list | tail -3
>  1ef | 08/17/2021 | 17:51:49 | Session Audit #0xff |  | Asserted
>  1f0 | 08/17/2021 | 18:52:11 | Watchdog2 #0xca | Timer interrupt () |
> Asserted
>  1f1 | 08/17/2021 | 18:52:46 | Watchdog2 #0xca | Power cycle () | Asserted
> root@r13aug21:/boot #
> 
> 
> 
> 

-- 
Alexander Motin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b6f97a7d-73ce-c3d3-ee56-5a7ae5bfed05>