[CRIU] ppc sets failed
Cyrill Gorcunov
gorcunov at gmail.com
Wed Feb 10 06:24:13 PST 2016
On Wed, Feb 10, 2016 at 05:22:51PM +0300, Cyrill Gorcunov wrote:
> On Wed, Feb 10, 2016 at 05:05:09PM +0300, Cyrill Gorcunov wrote:
> > On Wed, Feb 10, 2016 at 04:45:14PM +0300, Cyrill Gorcunov wrote:
> > > On Wed, Feb 10, 2016 at 04:39:05PM +0300, Pavel Emelyanov wrote:
> > > >
> > > > The issue is fixed with
> > > > https://github.com/xemul/criu/commit/c9393ec5dc290f164b6f9a446477f7e9e423920f
> > >
> > > Turned on. Thanks!
> >
> > (00.073410) Running post-restore scripts
> > (00.073434) Unlock network
> > pie: restoring seccomp mode 0 for 72
> > pie: Error (pie/restorer.c:236): Unable to restore capabilities: -1
> > (00.073765) Restore finished successfully. Resuming tasks.
> > (00.073809) 72 was trapped
> > (00.073829) 72 is going to execute the syscall 4
> > pie: Error (pie/restorer.c:1290): BUG at pie/restorer.c:1290
> > (00.073887) 72 was trapped
> > (00.073901) `- Expecting exit
> > (00.073953) Error (parasite-syscall.c:955): Task is in unexpected state: b7f
> > (00.073977) Writing stats
> >
> > Sigh. Hell knows why this happened. Didn't trigger before.
>
> Guys, something is broken. Here is what I got on current master and x86-64.
>
> [cyrill at uranus criu] sudo python test/zdtm.py run -t zdtm/live/static/remap_dead_pid_root
I think this is 'cause of resent rst_malloc changes.
More information about the CRIU
mailing list