From: Bjorn Helgaas <helgaas@kernel.org>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: linux-watchdog@vger.kernel.org, wim@linux-watchdog.org,
linux@roeck-us.net
Subject: Re: watchdog: how to enable?
Date: Mon, 18 Nov 2019 08:38:38 -0600 [thread overview]
Message-ID: <20191118143838.GA29359@google.com> (raw)
In-Reply-To: <CAHhAz+h6SuGKWn0qNqsCdNjDks_vHuJW-KfiQja_b3x8x=vq_A@mail.gmail.com>
[-cc linux-pci (nothing here is PCI-specific)]
On Sat, Nov 16, 2019 at 06:05:05AM +0530, Muni Sekhar wrote:
> My kernel is built with the following options:
>
> $ cat /boot/config-5.0.1 | grep NO_HZ
> CONFIG_NO_HZ_COMMON=y
> CONFIG_NO_HZ_IDLE=y
> # CONFIG_NO_HZ_FULL is not set
> CONFIG_NO_HZ=y
> CONFIG_RCU_FAST_NO_HZ=y
>
> I booted with watchdog enabled(nmi_watchdog=1) as given below:
>
> BOOT_IMAGE=/boot/vmlinuz-5.0.1
> root=UUID=f65454ae-3f1d-4b9e-b4be-74a29becbe1e ro debug
> ignore_loglevel console=ttyUSB0,115200 console=tty0 console=tty1
> console=ttyS2,115200 memmap=1M!1023M nmi_watchdog=1
> crashkernel=384M-:128M
>
> When the system is frozen or the kernel is locked up(I noticed that in
> this state kernel is not responding for ALT-SysRq-<command key>) but
> watchdog is not triggered. So I want to understand how to enable the
> watchdog timer and how to verify the basic watchdog functionality
> behavior?
I don't know much about the watchdog, but I assume you've found these
already?
Documentation/admin-guide/lockup-watchdogs.rst
Documentation/admin-guide/sysctl/kernel.rst
Do you have CONFIG_HAVE_NMI_WATCHDOG=y? (See arch/Kconfig)
next prev parent reply other threads:[~2019-11-18 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 0:35 watchdog: how to enable? Muni Sekhar
2019-11-16 1:04 ` Guenter Roeck
2019-11-16 3:03 ` Muni Sekhar
2019-11-16 16:01 ` Guenter Roeck
2019-11-16 18:34 ` Muni Sekhar
2019-11-16 21:42 ` Guenter Roeck
2019-11-18 9:52 ` Muni Sekhar
2019-11-18 14:10 ` Guenter Roeck
2019-11-18 15:07 ` Muni Sekhar
2019-11-18 14:38 ` Bjorn Helgaas [this message]
2019-11-18 14:41 ` Bjorn Helgaas
2019-11-18 15:09 ` Muni Sekhar
2019-11-22 10:59 ` Guenter Roeck
2019-11-22 12:54 ` Muni Sekhar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191118143838.GA29359@google.com \
--to=helgaas@kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=munisekharrms@gmail.com \
--cc=wim@linux-watchdog.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.