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.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, 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 12828C7618B for ; Thu, 25 Jul 2019 05:12:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DA20522BED for ; Thu, 25 Jul 2019 05:12:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="T5kP8fdS" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390504AbfGYFMX (ORCPT ); Thu, 25 Jul 2019 01:12:23 -0400 Received: from mail-ot1-f67.google.com ([209.85.210.67]:45023 "EHLO mail-ot1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390362AbfGYFMX (ORCPT ); Thu, 25 Jul 2019 01:12:23 -0400 Received: by mail-ot1-f67.google.com with SMTP id b7so202778otl.11 for ; Wed, 24 Jul 2019 22:12:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1HavsQi0PIVHE/5wuO+aYwrYRfGtBVcCZTVvBrVhq0E=; b=T5kP8fdSRTvshBPEpuaYQzIzZ0Jj23tcm7iIucIeecgMkiulRFwLMAXR2e/zS1ZaxB 2TxranTYalP9Xtp6W7AKARIETevKkOxvqPoKv0LMyqS7WjmNg5UbBGU2YIeRXI3fOeCO nMS/V5Z/OICrzQvpF46oN9Xf6rsvZZsTGvBExd3rEHgGoBh+Ccm1XPC7jo2Av2a7JRmT B6TpARwzD3pK3oPTAGjj8OjScwG3sN4uQ3ghRdVBPwHgV/v1ypdAGkhGqnqARow7EGvJ beSBKko4oteGiGErP91gRlEuY21dj/7JyizaA+dG7soVh4E7j14+aAroDgOKmpT8mewM DI4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1HavsQi0PIVHE/5wuO+aYwrYRfGtBVcCZTVvBrVhq0E=; b=VG2hAq8VO0S0j7ChuOGD6TK4z0xf95CQQpmk05v0b8kb0MSLlcbcLnpv4JWSSilLTf OwAwfoYLL1g73QBZufpx5A5HWri15JOi2DS6187gPUkWHrAJPzWmseTjlC7IGCiiZ0sd OA/SClqUMisrGZwq9+blpr07Q2jtgGsLr4qTRXYMxfiLqGYQrJ8RDqFFciWzYuMah1Ry dyiOsOeyfBM4E3hH/M9KGEtmk5xUA0tBSG7Xa7A74XttLRQ1Jv36ot9dPnPikgxJyZUd G/oAfmUOsDvHtKr2Mxp6weDoOFADmcL+nawSUd+JAD80zyDg6L+AUxAwGNy2owKEDV4M d9rQ== X-Gm-Message-State: APjAAAW/4JSQMqR0n4Jy7mUeCZkCnL3GW4AnT033ZDNmcQ1hVtNqx8kH macU1VYs1HXa4hnTTtPyE0WkLjHrZs4H/Gfj7vTtRtlm X-Google-Smtp-Source: APXvYqxdLT9oV7QDovoxb7mV+P1oX+U/iH6JkTiMg6gCWCBYNoPtI/odzhUUxblN8zSdZGOlpktt19+7ezSi3r6fL6o= X-Received: by 2002:a9d:2c26:: with SMTP id f35mr62787865otb.362.1564031542285; Wed, 24 Jul 2019 22:12:22 -0700 (PDT) MIME-Version: 1.0 References: <97817286-92ae-cd13-4cc1-7a0355140414@roeck-us.net> In-Reply-To: <97817286-92ae-cd13-4cc1-7a0355140414@roeck-us.net> From: Vignesh Raman Date: Thu, 25 Jul 2019 10:42:11 +0530 Message-ID: Subject: Re: watchdog: iTCO_wdt: failed to load To: Guenter Roeck Cc: linux-watchdog@vger.kernel.org, andriy.shevchenko@linux.intel.com, rajneesh.bhardwaj@linux.intel.com, mika.westerberg@linux.intel.com Content-Type: text/plain; charset="UTF-8" Sender: linux-watchdog-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-watchdog@vger.kernel.org Hi Guenter, On Wed, Jul 24, 2019 at 6:57 PM Guenter Roeck wrote: > > What is the output of /proc/iomem, what PCI devices does it have, and what are > the ACPI devices ? Reason for asking is that I don't immediately see the ACPI > or PCI devices associated with above patch in your dmesg. If not, the patch > might actually cause the watchdog in your system not to work. /proc/iomem - http://paste.debian.net/1092996/ PCI devices - http://paste.debian.net/1092997/ ACPI devices - http://paste.debian.net/1093003/ > Also, did this ever work in your system ? If it did work, did the failure > start after a kernel update or after a BIOS update ? The hardware watchdog has never worked in the system. Without the patch https://lore.kernel.org/patchwork/patch/770990/ the probe error is seen, [ 3.828440] iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff] [ 3.828803] iTCO_wdt: probe of iTCO_wdt failed with error -16 With the patch the module loads fine, but the hardware watchdog does not work. Regards, Vignesh