From: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Cc: "shuah@kernel.org" <shuah@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH for-next 1/3] selftests/watchdog: add count parameter for watchdog-test
Date: Mon, 28 Oct 2024 06:06:36 +0000 [thread overview]
Message-ID: <6862e399-b169-4ffb-b9c6-904f99d96e56@fujitsu.com> (raw)
In-Reply-To: <f10e8a78-3b50-4212-9b5d-ba99a3421379@linuxfoundation.org>
linux/tools/testing/selftests/watchdog# make run_tests
TAP version 13
1..1
# timeout set to 45
# selftests: watchdog: watchdog-test
# Watchdog Ticking Away!
# .............................................#
not ok 1 selftests: watchdog: watchdog-test # TIMEOUT 45 seconds
And i got warning in dmesg
[ 1953.229511] watchdog: watchdog0: watchdog did not stop!
On 28/10/2024 13:55, Shuah Khan wrote:
>>>>
>>>
>>> The system shouldn't reboot just because watchdog test is left running.
>>> watchdog test keeps calling ioctl() with WDIOC_KEEPALIVE to make sure
>>> the watchdog card timer is reset.
>>
>> Err..
>>
>> How watchdog test keep calling ioctl() with WDIOC_KEEPALIVE after ./watchdog_test has finished?
>>
>> In my understanding, the cause is that, ./watchdog_test didn't goto neither
>> A)
>> 347 end:
>> 348 /*
>> 349 * Send specific magic character 'V' just in case Magic Close is
>> 350 * enabled to ensure watchdog gets disabled on close.
>> 351 */
>> 352 ret = write(fd, &v, 1);
>> 353 if (ret < 0)
>> 354 printf("Stopping watchdog ticks failed (%d)...\n", errno);
>>
>> nor B)
>
> Can you send strace output from "make run_tests" from your system?
>
> thanks,
> -- Shuah
next prev parent reply other threads:[~2024-10-28 6:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 1:39 Li Zhijian
2024-10-25 1:39 ` [PATCH for-next 2/3] selftests/watchdog: exit watchdog-test with error code Li Zhijian
2024-10-25 1:39 ` [PATCH for-next 3/3] selftests/watchdog: Add run_watchdog-test.sh to run watchdog tests Li Zhijian
2024-10-27 0:28 ` [PATCH for-next 1/3] selftests/watchdog: add count parameter for watchdog-test Shuah Khan
2024-10-28 0:50 ` Zhijian Li (Fujitsu)
2024-10-28 3:29 ` Shuah Khan
2024-10-28 4:02 ` Zhijian Li (Fujitsu)
2024-10-28 5:31 ` Shuah Khan
2024-10-28 5:45 ` Zhijian Li (Fujitsu)
2024-10-28 5:55 ` Shuah Khan
2024-10-28 6:06 ` Zhijian Li (Fujitsu) [this message]
2024-10-28 6:25 ` Shuah Khan
2024-10-28 6:32 ` Zhijian Li (Fujitsu)
2024-10-28 6:44 ` Shuah Khan
2024-10-29 2:24 ` Shuah Khan
2024-10-29 3:03 ` Zhijian Li (Fujitsu)
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=6862e399-b169-4ffb-b9c6-904f99d96e56@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®