Linux-Watchdog Archive on lore.kernel.org
 help / color / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Muni Sekhar <munisekharrms@gmail.com>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-watchdog@vger.kernel.org, wim@linux-watchdog.org
Subject: Re: watchdog: how to enable?
Date: Fri, 22 Nov 2019 02:59:08 -0800
Message-ID: <f28024de-bfad-5f3e-6332-aebfa48991a8@roeck-us.net> (raw)
In-Reply-To: <CAHhAz+j7v-Utpir8wyCVORv_fthdLLg_spR_G+8TjBBSyJa6wA@mail.gmail.com>

On 11/18/19 7:09 AM, Muni Sekhar wrote:
> On Mon, Nov 18, 2019 at 8:08 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
>>
>> [-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)
> 
> I don’t have CONFIG_HAVE_NMI_WATCHDOG in kernel .config file.
> 

That would mean you don't have NMI in the first place. What is your
architecture ?

Guenter

> $cat /boot/config-5.0.1 | grep CONFIG_HAVE_NMI_WATCHDOG
> 
> But tried to enable CONFIG_HAVE_NMI_WATCHDOG via menuconfig, but could
> not able to find it. What is the role of CONFIG_HAVE_NMI_WATCHDOG?
> 
> Symbol: HAVE_NMI_WATCHDOG [=n]
> 
>                                              │
>    │ Type  : bool
> 
>                                                  │
>    │   Defined at arch/Kconfig:339
> 
>                                                  │
>    │   Depends on: HAVE_NMI [=y]
> 
>                                                  │
>    │   Selected by [n]:
> 
>                                                  │
>    │   - HAVE_HARDLOCKUP_DETECTOR_ARCH [=n]
> 
> 
>    │ Symbol: HAVE_HARDLOCKUP_DETECTOR_ARCH [=n]
> 
>                                                  │
>    │ Type  : bool
> 
>                                                  │
>    │   Defined at arch/Kconfig:346
> 
>                                                  │
>    │   Selects: HAVE_NMI_WATCHDOG [=n]
> 
> 
> 
> 
> 


  reply index

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-16  0:35 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
2019-11-18 14:41   ` Bjorn Helgaas
2019-11-18 15:09   ` Muni Sekhar
2019-11-22 10:59     ` Guenter Roeck [this message]
2019-11-22 12:54       ` Muni Sekhar

Reply instructions:

You may reply publically 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=f28024de-bfad-5f3e-6332-aebfa48991a8@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=helgaas@kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --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

Linux-Watchdog Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-watchdog/0 linux-watchdog/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-watchdog linux-watchdog/ https://lore.kernel.org/linux-watchdog \
		linux-watchdog@vger.kernel.org
	public-inbox-index linux-watchdog

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-watchdog


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git