• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 741 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

omap_wdt.c watchdog

Oleg Belogolov
Expert 3865 points


Hi Team,

it seems that after the booting of kernel the watchdog is started but is activated only after the /dev/watchdog is opened.

That means that the system crash before the watchdog was activated will not be detected.

Is there a kernel option that activates the watchdog from beginning of booting?

Thanks and regards,

Oleg

  • 0
    TI__Guru** 116100 points

    Hi Oleg,

    1) You can use "panic" u-boot's bootcmd variable to detect panics & oops to reboot the board.

    Ex:

    panic=10; it will reboot the device after 10 seconds if any panic or oops occurred.

    2) Are you passing any bootcmd variable or WDT driver ?

    something like that,

    omap_wdt.timer_margin=30


    Actually the WDT expires based on the above variable and it should be adjusted through the WDT daemon from filesystem.

  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 370 points

    Hi All,

    we're aware of the panic boot variable and actually use it. But, this does not save you from all cases. In some, only the watchdog will be able to get you back.

    Regarding 2) I modified the boot arguments as suggested but this does not show the expected effect. Maybe I'm doing something wrong. Giving omap_wdt.timer_margin=30 as bootcmd variable does not prevent that the system hangs infinitely after a bad crash, i.e. watchdog is not really running. 

    What we want is to have the watchdog running from the moment on the watchdog driver is loaded, and, that it is triggered by the watchdog driver until somebody opens /dev/watchdog

    Sam