From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3D407C2D0DB for ; Wed, 29 Jan 2020 17:22:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 664C82070E for ; Wed, 29 Jan 2020 17:22:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=fpond.eu header.i=@fpond.eu header.b="M+Ip3A2m" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726733AbgA2RWY (ORCPT ); Wed, 29 Jan 2020 12:22:24 -0500 Received: from mo4-p00-ob.smtp.rzone.de ([81.169.146.216]:17988 "EHLO mo4-p00-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726679AbgA2RWY (ORCPT ); Wed, 29 Jan 2020 12:22:24 -0500 X-Greylist: delayed 362 seconds by postgrey-1.27 at vger.kernel.org; Wed, 29 Jan 2020 12:22:23 EST DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1580318542; s=strato-dkim-0002; d=fpond.eu; h=Subject:Message-ID:Cc:To:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH:From: Subject:Sender; bh=1VqhDXWE4agoMp60ZLl5kMTFU0+HK7qMeOqkwhfAO/U=; b=M+Ip3A2mutDvBh3+Wev51iM0feGZWtTW97e6pjXcqcPr6YBqsIVnGrg2JM9j6Q31qT tJgzsNVcZfBrIZRk0WwoUSki7xqil0kBXELayZA9jl4n2qdqXrdBtw0cDO2f6w1kbsBR 2wEOmMmLa1mxYMHh9ThvyHIUBh+QMiQhUWCJnmHz4eD7t6uMeJQn+uGnoAyVdxc2SYwJ LyhPX5jKl7lB055DD87OkCW7o4IDsSQgycsLXs13f6rJGWF+mYvIlVm9GSAtzme5C0Yy 4OFurOEvhUHIhMVnZpaqPob5EUQfq58o0/SS28eNturPbroj4y1HIlPklJpQMiTQF6se p9Ww== X-RZG-AUTH: ":OWANVUa4dPFUgKR/3dpvnYP0Np73amq+g13rqGzvv3qxio1R8fCs/83N2Y0=" X-RZG-CLASS-ID: mo00 Received: from oxapp05-01.back.ox.d0m.de by smtp-ox.front (RZmta 46.1.8 AUTH) with ESMTPSA id N0955aw0THGJ0YC (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve X9_62_prime256v1 with 256 ECDH bits, eq. 3072 bits RSA)) (Client did not present a certificate); Wed, 29 Jan 2020 18:16:19 +0100 (CET) Date: Wed, 29 Jan 2020 18:16:19 +0100 (CET) From: Ulrich Hecht To: linux-watchdog@vger.kernel.org Cc: wsa@the-dreams.de Message-ID: <1731064051.261328.1580318179697@webmail.strato.com> Subject: Best practice when probe fails on armed watchdog? MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.1-Rev25 X-Originating-Client: open-xchange-appsuite Sender: linux-watchdog-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-watchdog@vger.kernel.org Hi! What is the right thing to do when a watchdog device that has been armed by the bootloader fails to probe? Should the driver - disable the device and thus save the system from being torn down by a potentially malfunctioning watchdog, at the risk of missing issues further down the line, or - leave it as is (even though that would most likely result in a reset), hoping that the error is either transient or that there is a mechanism in place outside the kernel that will resolve it? Is there a best practice for this case? CU Uli