Re: [Xen-devel] [xen-unstable test] 122968: regressions - FAIL

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, May 22, 2018 at 07:20:32AM +0200, Juergen Gross wrote:
> On 22/05/18 01:59, osstest service owner wrote:
> > flight 122968 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/122968/
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 16 
> > guest-localmigrate/x10 fail REGR. vs. 122804
> 
> This seems to be a kernel issue:
> 
> [  349.264490] Freezing user space processes ... (elapsed 0.004 seconds)
> done.
> [  349.277385] Freezing remaining freezable tasks ...
> [  369.285006] Freezing of tasks failed after 20.002 seconds (1 tasks
> refusing to freeze, wq_busy=0):
> [  369.293150] jbd2/xvda5-8    D 0000000000000000     0   115      2
> 0x00000000
> [  369.299858]  ffff8800001fd590 0000000000000046 0000000000013200
> ffff88002ea3ffd8
> [  369.307084]  0000000000013200 ffff8800001fd590 ffff88002f813ab0
> ffff88002fbd7140
> [  369.314260]  0000000000000002 ffffffff811df230 ffff88002ea3fc80
> ffff880029f64398
> [  369.321462] Call Trace:
> [  369.323726]  [<ffffffff811df230>] ? generic_block_bmap+0x50/0x50
> [  369.329144]  [<ffffffff815217e9>] ? io_schedule+0x99/0x120
> [  369.334118]  [<ffffffff811df23a>] ? sleep_on_buffer+0xa/0x10
> [  369.339259]  [<ffffffff81521b6c>] ? __wait_on_bit+0x5c/0x90
> [  369.344304]  [<ffffffff811df230>] ? generic_block_bmap+0x50/0x50
> [  369.349782]  [<ffffffff81521c17>] ? out_of_line_wait_on_bit+0x77/0x90
> [  369.355718]  [<ffffffff810abc90>] ? autoremove_wake_function+0x30/0x30
> [  369.361624]  [<ffffffffa01605aa>] ?
> jbd2_journal_commit_transaction+0x182a/0x1a30 [jbd2]
> [  369.368948]  [<ffffffffa0163e42>] ? kjournald2+0xb2/0x240 [jbd2]
> [  369.374387]  [<ffffffff810abc60>] ? prepare_to_wait_event+0xf0/0xf0
> [  369.380082]  [<ffffffffa0163d90>] ? commit_timeout+0x10/0x10 [jbd2]
> [  369.385805]  [<ffffffff8108b13d>] ? kthread+0xbd/0xe0
> [  369.390470]  [<ffffffff8108b080>] ? kthread_create_on_node+0x180/0x180
> [  369.396412]  [<ffffffff81524c58>] ? ret_from_fork+0x58/0x90
> [  369.401489]  [<ffffffff8108b080>] ? kthread_create_on_node+0x180/0x180
> [  369.407450]
> [  369.408916] Restarting kernel threads ... done.
> [  369.413308] xen:manage: do_suspend: freeze kernel threads failed -16
> [  369.420958] Restarting tasks ... done.
> 
> Which kernel version is that?

Debian Jessie's stock kernel: 3.16.x

> 
> 
> >  test-amd64-amd64-xl-qemut-ws16-amd64 13 guest-saverestore fail REGR. vs. 
> > 122804
> 
> Can someone from tools side look at this, please?
> 
> xc: error: Failed to get types for pfn batch (14 = Bad address):
> Internal error
> xc: error: Save failed (14 = Bad address): Internal error
> 

We have a theory: Windows issues reboot in the middle of a migration. Xl
needs more locking.

I wrote a series to start a discussion that but it hasn't got much
attention.

 [RFC PATCH 0/4] Per-domain locking in xl
 <20170614171921.17475-1-wei.liu2@xxxxxxxxxx>

> >  test-armhf-armhf-libvirt     19 leak-check/check         fail REGR. vs. 
> > 122804
> 
> Bad timing/missing whitelist?
> 
> 2018-05-20 06:25:03 Z LEAKED [process 25641 /bin/sh] process: root
> 25641 25637  0 06:25 ?        00:00:00 /bin/sh -c test -x
> /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
> 2018-05-20 06:25:03 Z LEAKED [process 25644 /bin/sh] process: root
> 25644 25642  0 06:25 ?        00:00:00 /bin/sh /etc/cron.daily/apt
> 2018-05-20 06:25:03 Z LEAKED [process 25637 /usr/sbin/CRON] process:
> root     25637  1298  0 06:25 ?        00:00:00 /usr/sbin/CRON
> 2018-05-20 06:25:03 Z LEAKED [process 25663 apt-get] process: root
> 25663 25644  8 06:25 ?        00:00:00 apt-get check -qq
> 2018-05-20 06:25:03 Z LEAKED [process 25642 run-parts] process: root
> 25642 25641  0 06:25 ?        00:00:00 run-parts --report /etc/cron.daily
> 

Yes this is just unlucky.

> 
> Juergen
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel