29 Mar, 2011

1 commit

  • This is needed for determining the reason for failure when a softdog
    timeout occurs.

    We use softdog to watch for critical application failures and at the
    minimum a snapshot of the system would help to determine the cause. In
    such a scenario the application could fail but there isn't a softlockup as
    such, hence the detect softlockup feature does not help.

    The patch adds a module parameter soft_panic which when set to 1 causes
    softdog to invoke panic instead of reboot when the softdog timer expires.
    By invoking panic we execute kdump if it is configured and the vmcore
    generated by kdump should provide atleast a minimal idea of the reason for
    failure.

    Based on an original patch by Ken Sugawara
    Signed-off-by: Anithra P J
    Reviewed-by: WANG Cong
    Acked-by: Alan Cox
    Signed-off-by: Wim Van Sebroeck
    Signed-off-by: Andrew Morton

    Anithra P Janakiraman
     

16 Mar, 2011

1 commit


18 Jun, 2009

1 commit


25 Mar, 2009

1 commit


29 Oct, 2008

1 commit


06 Aug, 2008

1 commit

  • This brings the watchdog drivers into line with coding style.
    This patch takes cares of the indentation as described in chapter 1.
    Main changes:
    * Re-structure the ioctl switch call for all drivers as follows:
    switch (cmd) {
    case WDIOC_GETSUPPORT:
    case WDIOC_GETSTATUS:
    case WDIOC_GETBOOTSTATUS:
    case WDIOC_GETTEMP:
    case WDIOC_SETOPTIONS:
    case WDIOC_KEEPALIVE:
    case WDIOC_SETTIMEOUT:
    case WDIOC_GETTIMEOUT:
    case WDIOC_GETTIMELEFT:
    default:
    }

    This to make the migration from the drivers to the uniform watchdog
    device driver easier in the future.

    Signed-off-by: Wim Van Sebroeck

    Wim Van Sebroeck
     

21 Jun, 2008

1 commit


18 Oct, 2007

1 commit