Re: armv7 kyua runs via chroot on aarch64: zfs tests leave behind processes from timed out tests
On Aug 3, 2023, at 00:19, Mark Millard wrote:
> This is after the patch (leading whitespace might
> not have been preserved in what you see):
>
> # git -C /usr/main-src/ diff sys/dev/md/
> diff --git a/sys/dev/md/md.c b/sys/dev/md/md.c
> index a719dccb1955..365296ec4276 100644
> --- a/sys/dev/md/md.c
> +++ b/sys/dev/md/md.c
> @@ -147,8 +147,15 @@ struct md_ioctl32 {
>int md_fwsectors;
>uint32_tmd_label;
>int md_pad[MDNPAD];
> +#ifdef __aarch64__
> + uint32_tmd_pad0;
> +#endif
> } __attribute__((__packed__));
> +#ifdef __aarch64__
> +CTASSERT((sizeof(struct md_ioctl32)) == 440);
> +#else
> CTASSERT((sizeof(struct md_ioctl32)) == 436);
> +#endif
>
> #defineMDIOCATTACH_32 _IOC_NEWTYPE(MDIOCATTACH, struct md_ioctl32)
> #defineMDIOCDETACH_32 _IOC_NEWTYPE(MDIOCDETACH, struct md_ioctl32)
>
>
> The kyua run is still in process, but at this point there is
> the following accumulation from the zfs testing timouts:
>
> # ps -alxdww
> UID PID PPID C PRI NI VSZ RSS MWCHAN STAT TTTIME COMMAND
> . . .
> 0 17491 1 6 20 0 36460 12324 -T - 0:24.71 |--
> fsync_integrity /testdir2316/testfile2316
> 0 17551 1 5 20 0 10600 7512 tx->tx_s D - 0:00.00 |--
> /sbin/zpool destroy -f testpool.2316
> 0 17739 1 7 20 0 10600 7308 zfs tear D - 0:00.00 |--
> /sbin/zpool destroy -f testpool.2316
> 0 17841 1 3 20 0 10600 7316 tx->tx_s D - 0:00.00 |--
> /sbin/zpool destroy -f testpool.2316
> 0 17860 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17888 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17907 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17928 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17955 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17976 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17995 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18023 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18043 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18064 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18085 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18114 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18135 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18157 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18177 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18205 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18224 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18255 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18275 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18296 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18317 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18345 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18365 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18386 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18412 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18447 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18466 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18516 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18535 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18632 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
>
> Lots of these are from 300s timeouts but some are from 1200s or
> 1800s or 3600s timeouts.
>
> For reference:
>
> sys/cddl/zfs/tests/txg_integrity/txg_integrity_test:fsync_integrity_001_pos
> -> broken: Test case body timed out [1800.053s]
> sys/cddl/zfs/tests/txg_integrity/txg_integrity_test:txg_integrity_001_pos ->
> passed [63.702s]
> sys/cddl/zfs/tests/userquota/userquota_test:groupspace_001_pos -> skipped:
> Required program 'runwattr' not found in PATH [0.003s]
> sys/cddl/zfs/tests/userquota/userquota_test:groupspace_002_pos -> skipped:
> Required program 'runwattr' not found in PATH [0.002s]
>
Re: armv7 kyua runs via chroot on aarch64: zfs tests leave behind processes from timed out tests
On Aug 7, 2023, at 11:29, Enji Cooper wrote:
>
>
>> On Aug 3, 2023, at 10:20 AM, Mark Millard wrote:
>>
>> .. .
>
> Hi Mark,
> Could you please submit bugs and CC freebsd-testing or another appropriate
> mailing list? It looks like there are some Arm64 architecture specific issues
> that need to be addressed based on the limited information I have from these
> emails.
> Do you have DEADLKRES/INVARIANTS/WITNESS compiled into your kernel? If not,
> could you please do that?
> If that doesn’t give any helpful hints, could you please panic the kernel and
> dump some debug info from ddb, e.g.,
> 1. alltrace
> 2. show allchains
> 3. show alllocks
I tend to submit only once/if I've done the work to
establish the problems in snapshots or other such
that do not involve my builds. Submitting only based
on my builds is a means of last resort for me. Also,
when a bunch of issues are showing up in the same
time frame, I tend to start with a subset and let
others sit for a time until I get to them. There are
a bunch pending at this point. I'm more willing to
report to the lists based on less information and
a longer time frame to having more information,
largely in case it prompts others that have related
observations or the like.
My recent submittals for cortex-A7 (armv7) kyua run
related panics are:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272965
("armv7 'Alignment Fault' on read panic during udp_input for
kyua's sys/netinet6/exthdr:exthdr ; other udp_input related
panics")
and:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272966
("armv7 Kernel page fault with non-sleepable locks held panic
during in6ifa_ifwithaddr for kyua's sys/netpfil/pf/killstate:v6;
more tests too")
An interesting oddity is that, in my somewhat older
environment, I do not get the udp_input related panics
(272965). I only got those with the snapshot (while
trying to gather information to create the other submital
[272966]).
Michal Meloun has been having me test patches related
to these. But I could only effectively test the 272966
cases in the context I have, given that "interesting
oddity". (Michal also originally thought the 2 reports
were duplicates of each other. But they are not, at
least in my builds.)
I'll note that the "non-sleepable locks" is more of
an identification of context than a cause: it is from
part of the code that handles an alignment abort (that
shows up in the console output somewhat later), or
so I've been told.
It is true that I normally run non-debug builds. But
my normal build procedure builds both ways and I
substitute (install) the relevant debug build (WITNESS
and such included) when I get to the point that I'd
use it to advantage. My testing of Michal's patches
are based on my debug-build context.
===
Mark Millard
marklmi at yahoo.com
Re: armv7 kyua runs via chroot on aarch64: zfs tests leave behind processes from timed out tests
> On Aug 3, 2023, at 10:20 AM, Mark Millard wrote:
>
> On Aug 3, 2023, at 07:18, Mark Millard wrote:
>
>> On Aug 3, 2023, at 00:19, Mark Millard wrote:
>>
>>> This is after the patch (leading whitespace might
>>> not have been preserved in what you see):
>>>
>>> # git -C /usr/main-src/ diff sys/dev/md/
>>> diff --git a/sys/dev/md/md.c b/sys/dev/md/md.c
>>> index a719dccb1955..365296ec4276 100644
>>> --- a/sys/dev/md/md.c
>>> +++ b/sys/dev/md/md.c
>>> @@ -147,8 +147,15 @@ struct md_ioctl32 {
>>> int md_fwsectors;
>>> uint32_tmd_label;
>>> int md_pad[MDNPAD];
>>> +#ifdef __aarch64__
>>> + uint32_tmd_pad0;
>>> +#endif
>>> } __attribute__((__packed__));
>>> +#ifdef __aarch64__
>>> +CTASSERT((sizeof(struct md_ioctl32)) == 440);
>>> +#else
>>> CTASSERT((sizeof(struct md_ioctl32)) == 436);
>>> +#endif
>>>
>>> #defineMDIOCATTACH_32 _IOC_NEWTYPE(MDIOCATTACH, struct md_ioctl32)
>>> #defineMDIOCDETACH_32 _IOC_NEWTYPE(MDIOCDETACH, struct md_ioctl32)
>>>
>>>
>>> The kyua run is still in process, but at this point there is
>>> the following accumulation from the zfs testing timouts:
>>>
>>> # ps -alxdww
>>> UID PID PPID C PRI NI VSZ RSS MWCHAN STAT TTTIME COMMAND
>>> . . .
>>> 0 17491 1 6 20 0 36460 12324 -T - 0:24.71 |--
>>> fsync_integrity /testdir2316/testfile2316
>>> 0 17551 1 5 20 0 10600 7512 tx->tx_s D - 0:00.00 |--
>>> /sbin/zpool destroy -f testpool.2316
>>> 0 17739 1 7 20 0 10600 7308 zfs tear D - 0:00.00 |--
>>> /sbin/zpool destroy -f testpool.2316
>>> 0 17841 1 3 20 0 10600 7316 tx->tx_s D - 0:00.00 |--
>>> /sbin/zpool destroy -f testpool.2316
>>> 0 17860 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 17888 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 17907 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 17928 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 17955 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 17976 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 17995 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18023 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18043 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18064 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18085 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18114 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18135 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18157 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18177 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18205 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18224 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18255 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18275 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18296 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18317 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18345 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18365 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18386 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18412 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18447 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18466 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18516 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18535 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>> 0 18632 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
>>> /sbin/zfs upgrade
>>
>> It has added:
>>
>> 0 18656 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18748 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18767 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18858 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
Re: armv7 kyua runs via chroot on aarch64: zfs tests leave behind processes from timed out tests
On Aug 3, 2023, at 07:18, Mark Millard wrote:
> On Aug 3, 2023, at 00:19, Mark Millard wrote:
>
>> This is after the patch (leading whitespace might
>> not have been preserved in what you see):
>>
>> # git -C /usr/main-src/ diff sys/dev/md/
>> diff --git a/sys/dev/md/md.c b/sys/dev/md/md.c
>> index a719dccb1955..365296ec4276 100644
>> --- a/sys/dev/md/md.c
>> +++ b/sys/dev/md/md.c
>> @@ -147,8 +147,15 @@ struct md_ioctl32 {
>> int md_fwsectors;
>> uint32_tmd_label;
>> int md_pad[MDNPAD];
>> +#ifdef __aarch64__
>> + uint32_tmd_pad0;
>> +#endif
>> } __attribute__((__packed__));
>> +#ifdef __aarch64__
>> +CTASSERT((sizeof(struct md_ioctl32)) == 440);
>> +#else
>> CTASSERT((sizeof(struct md_ioctl32)) == 436);
>> +#endif
>>
>> #defineMDIOCATTACH_32 _IOC_NEWTYPE(MDIOCATTACH, struct md_ioctl32)
>> #defineMDIOCDETACH_32 _IOC_NEWTYPE(MDIOCDETACH, struct md_ioctl32)
>>
>>
>> The kyua run is still in process, but at this point there is
>> the following accumulation from the zfs testing timouts:
>>
>> # ps -alxdww
>> UID PID PPID C PRI NI VSZ RSS MWCHAN STAT TTTIME COMMAND
>> . . .
>> 0 17491 1 6 20 0 36460 12324 -T - 0:24.71 |--
>> fsync_integrity /testdir2316/testfile2316
>> 0 17551 1 5 20 0 10600 7512 tx->tx_s D - 0:00.00 |--
>> /sbin/zpool destroy -f testpool.2316
>> 0 17739 1 7 20 0 10600 7308 zfs tear D - 0:00.00 |--
>> /sbin/zpool destroy -f testpool.2316
>> 0 17841 1 3 20 0 10600 7316 tx->tx_s D - 0:00.00 |--
>> /sbin/zpool destroy -f testpool.2316
>> 0 17860 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 17888 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 17907 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 17928 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 17955 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 17976 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 17995 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18023 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18043 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18064 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18085 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18114 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18135 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18157 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18177 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18205 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18224 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18255 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18275 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18296 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18317 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18345 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18365 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18386 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18412 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18447 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18466 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18516 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18535 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>> 0 18632 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
>> /sbin/zfs upgrade
>
> It has added:
>
> 0 18656 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18748 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18767 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18858 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18877 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18907 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
Re: armv7 kyua runs via chroot on aarch64: zfs tests leave behind processes from timed out tests
On Aug 3, 2023, at 00:19, Mark Millard wrote:
> This is after the patch (leading whitespace might
> not have been preserved in what you see):
>
> # git -C /usr/main-src/ diff sys/dev/md/
> diff --git a/sys/dev/md/md.c b/sys/dev/md/md.c
> index a719dccb1955..365296ec4276 100644
> --- a/sys/dev/md/md.c
> +++ b/sys/dev/md/md.c
> @@ -147,8 +147,15 @@ struct md_ioctl32 {
>int md_fwsectors;
>uint32_tmd_label;
>int md_pad[MDNPAD];
> +#ifdef __aarch64__
> + uint32_tmd_pad0;
> +#endif
> } __attribute__((__packed__));
> +#ifdef __aarch64__
> +CTASSERT((sizeof(struct md_ioctl32)) == 440);
> +#else
> CTASSERT((sizeof(struct md_ioctl32)) == 436);
> +#endif
>
> #defineMDIOCATTACH_32 _IOC_NEWTYPE(MDIOCATTACH, struct md_ioctl32)
> #defineMDIOCDETACH_32 _IOC_NEWTYPE(MDIOCDETACH, struct md_ioctl32)
>
>
> The kyua run is still in process, but at this point there is
> the following accumulation from the zfs testing timouts:
>
> # ps -alxdww
> UID PID PPID C PRI NI VSZ RSS MWCHAN STAT TTTIME COMMAND
> . . .
> 0 17491 1 6 20 0 36460 12324 -T - 0:24.71 |--
> fsync_integrity /testdir2316/testfile2316
> 0 17551 1 5 20 0 10600 7512 tx->tx_s D - 0:00.00 |--
> /sbin/zpool destroy -f testpool.2316
> 0 17739 1 7 20 0 10600 7308 zfs tear D - 0:00.00 |--
> /sbin/zpool destroy -f testpool.2316
> 0 17841 1 3 20 0 10600 7316 tx->tx_s D - 0:00.00 |--
> /sbin/zpool destroy -f testpool.2316
> 0 17860 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17888 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17907 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17928 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17955 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17976 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 17995 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18023 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18043 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18064 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18085 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18114 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18135 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18157 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18177 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18205 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18224 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18255 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18275 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18296 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18317 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18345 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18365 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18386 1 3 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18412 1 1 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18447 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18466 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18516 1 6 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18535 1 2 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
> 0 18632 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
> /sbin/zfs upgrade
It has added:
0 18656 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
/sbin/zfs upgrade
0 18748 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
/sbin/zfs upgrade
0 18767 1 4 20 0 10080 6956 spa_name D - 0:00.00 |--
/sbin/zfs upgrade
0 18858 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
/sbin/zfs upgrade
0 18877 1 0 20 0 10080 6956 spa_name D - 0:00.00 |--
/sbin/zfs upgrade
0 18907 1 7 20 0 10080 6956 spa_name D - 0:00.00 |--
/sbin/zfs upgrade
0 18926 1 5 20 0 10080 6956 spa_name D - 0:00.00 |--
/sbin/zfs upgrade
0 18956 1 7 20 0
armv7 kyua runs via chroot on aarch64: zfs tests leave behind processes from timed out tests
This is after the patch (leading whitespace might
not have been preserved in what you see):
# git -C /usr/main-src/ diff sys/dev/md/
diff --git a/sys/dev/md/md.c b/sys/dev/md/md.c
index a719dccb1955..365296ec4276 100644
--- a/sys/dev/md/md.c
+++ b/sys/dev/md/md.c
@@ -147,8 +147,15 @@ struct md_ioctl32 {
int md_fwsectors;
uint32_tmd_label;
int md_pad[MDNPAD];
+#ifdef __aarch64__
+ uint32_tmd_pad0;
+#endif
} __attribute__((__packed__));
+#ifdef __aarch64__
+CTASSERT((sizeof(struct md_ioctl32)) == 440);
+#else
CTASSERT((sizeof(struct md_ioctl32)) == 436);
+#endif
#defineMDIOCATTACH_32 _IOC_NEWTYPE(MDIOCATTACH, struct md_ioctl32)
#defineMDIOCDETACH_32 _IOC_NEWTYPE(MDIOCDETACH, struct md_ioctl32)
The kyua run is still in process, but at this point there is
the following accumulation from the zfs testing timouts:
# ps -alxdww
UID PID PPID C PRI NI VSZ RSS MWCHAN STAT TTTIME COMMAND
. . .
0 17491 1 6 20 0 36460 12324 -T - 0:24.71 |--
fsync_integrity /testdir2316/testfile2316
0 17551 1 5 20 0 10600 7512 tx->tx_s D - 0:00.00 |--
/sbin/zpool destroy -f testpool.2316
0 17739 1 7 20 0 10600 7308 zfs tear D - 0:00.00 |--
/sbin/zpool destroy -f testpool.2316
0 17841 1 3 20 0 10600 7316 tx->tx_s D - 0:00.00 |--
/sbin/zpool destroy -f testpool.2316
0 17860 1 0 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 17888 1 3 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 17907 1 6 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 17928 1 7 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 17955 1 0 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 17976 1 4 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 17995 1 2 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18023 1 2 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18043 1 2 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18064 1 3 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18085 1 0 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18114 1 7 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18135 1 2 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18157 1 6 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18177 1 6 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18205 1 4 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18224 1 1 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18255 1 3 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18275 1 1 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18296 1 5 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18317 1 4 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18345 1 4 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18365 1 2 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18386 1 3 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18412 1 1 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18447 1 5 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18466 1 5 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18516 1 6 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18535 1 2 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
0 18632 1 0 20 0 10080 6956 spa_name D - 0:00.00 |-- /sbin/zfs
upgrade
Lots of these are from 300s timeouts but some are from 1200s or
1800s or 3600s timeouts.
For reference:
sys/cddl/zfs/tests/txg_integrity/txg_integrity_test:fsync_integrity_001_pos ->
broken: Test case body timed out [1800.053s]
sys/cddl/zfs/tests/txg_integrity/txg_integrity_test:txg_integrity_001_pos ->
passed [63.702s]
sys/cddl/zfs/tests/userquota/userquota_test:groupspace_001_pos -> skipped:
Required program 'runwattr' not found in PATH [0.003s]
sys/cddl/zfs/tests/userquota/userquota_test:groupspace_002_pos -> skipped:
Required program 'runwattr' not found in PATH [0.002s]
sys/cddl/zfs/tests/userquota/userquota_test:userquota_001_pos -> skipped:
Required program 'runwattr' not found in PATH [0.002s]
sys/cddl/zfs/tests/userquota/userquota_test:userquota_002_pos -> broken: Test
case cleanup timed out [0.148s]
