[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6862e399-b169-4ffb-b9c6-904f99d96e56@fujitsu.com>
Date: Mon, 28 Oct 2024 06:06:36 +0000
From: "Zhijian Li (Fujitsu)" <lizhijian@...itsu.com>
To: Shuah Khan <skhan@...uxfoundation.org>, "linux-kselftest@...r.kernel.org"
<linux-kselftest@...r.kernel.org>
CC: "shuah@...nel.org" <shuah@...nel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH for-next 1/3] selftests/watchdog: add count parameter for
watchdog-test
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
Powered by blists - more mailing lists