Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > muc.lists.freebsd.hardware > #1978

Re: watchdog timer programming

From Stephane Rochoy <stephane.rochoy@stormshield.eu>
Newsgroups muc.lists.freebsd.hardware
Subject Re: watchdog timer programming
Date 2024-09-27 15:55 +0200
Organization Newsgate at muc.de e.V.
Message-ID <868qvddwph.fsf@cthulhu.stephaner.labo.int> (permalink)
References (2 earlier) <86plotbk5b.fsf@cthulhu.stephaner.labo.int> <78e9461c-b93d-403f-b3a1-3568548b9283@sentex.net> <9008b389-ab06-401d-9a95-84f849ca602a@sentex.net> <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> <86plosdv48.fsf@cthulhu.stephaner.labo.int>

Show all headers | View raw


mike tancsa <mike@sentex.net> writes:

> I also started to play around with the non hardware based 
> watchdog
> timer.  For some reason, I cant get the box to reboot. It just 
> prints a
> stack trace and continues
>
> This is with no driver loaded.
>
> 0{t}# watchdogd --softtimeout-action panic -t 5
> 0{t}# ps -auxww | grep dog
> root     1487   0.4  0.2   12820  12920  -  S<s  09:03 0:00.01 
> watchdogd
> --softtimeout-action panic -t 5
> root     1489   0.0  0.0   12808   2636 u0  S+   09:03 
> 0:00.00
> grep dog
> 0{t}# kill -9 1487
> 0{t}# KDB: stack backtrace:
> #0 0xffffffff80b7fefd at kdb_backtrace+0x5d
> #1 0xffffffff80abec93 at hardclock+0x103
> #2 0xffffffff80abfe8b at handleevents+0xab
> #3 0xffffffff80ac0b7c at timercb+0x24c
> #4 0xffffffff810d0ebb at lapic_handle_timer+0xab
> #5 0xffffffff80fd8a71 at Xtimerint+0xb1
> #6 0xffffffff804b3685 at acpi_cpu_idle+0x2c5
> #7 0xffffffff80fc48f6 at cpu_idle_acpi+0x46
> #8 0xffffffff80fc49ad at cpu_idle+0x9d
> #9 0xffffffff80b67bb6 at sched_idletd+0x576
> #10 0xffffffff80aecf7f at fork_exit+0x7f
> #11 0xffffffff80fd7dae at fork_trampoline+0xe
>
> 0{t}#
>
> Should it not reboot at this point ?

I don't think so. `kdb_backtrace` being involved let me think the
kernel was compiled with KDB. You should play with ddb(8) to set a
default action like reset when entering kdb.

Regards,
-- 
Stéphane Rochoy
O: Stormshield


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

Back to muc.lists.freebsd.hardware | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: watchdog timer programming Stephane Rochoy <stephane.rochoy@stormshield.eu> - 2024-09-24 08:46 +0200
  Re: watchdog timer programming Stephane Rochoy <stephane.rochoy@stormshield.eu> - 2024-09-25 09:13 +0200
    Re: watchdog timer programming Stephane Rochoy <stephane.rochoy@stormshield.eu> - 2024-09-27 08:09 +0200
    Re: watchdog timer programming Stephane Rochoy <stephane.rochoy@stormshield.eu> - 2024-09-27 15:55 +0200
      Re: watchdog timer programming Stephane Rochoy <stephane.rochoy@stormshield.eu> - 2024-09-30 09:18 +0200
      Re: watchdog timer programming Stephane Rochoy <stephane.rochoy@stormshield.eu> - 2024-10-01 08:07 +0200
  Re: watchdog timer programming (progress) Stephane Rochoy <stephane.rochoy@stormshield.eu> - 2024-10-02 11:13 +0200

csiph-web