[CRIU] few remaining s390 zdtm failures (for me)
Pavel Emelyanov
xemul at virtuozzo.com
Wed Aug 9 19:11:45 MSK 2017
On 08/08/2017 02:40 PM, Adrian Reber wrote:
> Running on RHEL s390x I have few zdtm test cases failing which do not
> fail on x86_64 and ppc64le.
>
> * zdtm/static/vdso02(ns)
> * zdtm/static/stopped(h)
> * zdtm/static/stopped01(h)
> * zdtm/static/stopped02(h)
> * zdtm/static/stopped12(ns)
>
> Error messages are all the same like:
>
> (01.503563) cg: Set 1 is criu one
> (01.503686) Seized task 24, state 1
> (01.503715) Collected (4 attempts, 0 in_progress)
> (01.503728) Seized task 25, state 0
> (01.503912) Error (compel/src/lib/infect.c:180): SEIZE 25: task not stopped after seize
Can you put task_is_trapped()-like messages in this place so that we could
see what's wrong with this task?
> (01.503921) Error (compel/src/lib/infect.c:309): Unable to detach from 25: No such process
>
> All other tests are working. I guess I might be missing an
> s390x related backport on my 3.10.x kernel.
>
> Any ideas which backports might be missing? Or what I need to look for?
>
> Adrian
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu
> .
>
More information about the CRIU
mailing list