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

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, May 22, 2018 at 02:34:37PM +0200, Juergen Gross wrote:
> On 22/05/18 12:28, Wei Liu wrote:
> > 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
> 
> Hmm, you seem to have hit this problem before:
> 
> https://lists.xen.org/archives/html/xen-devel/2017-10/msg02235.html
> 
> Back then you blamed the rather new 4.9 kernel...
> 

Yeah, I did see that on 4.9 -- that report was when I used stretch as
guest during my attempt to upgrade osstest to stretch. The production
osstest still uses jessie.

Maybe this is a long standing bug in Linux?

Wei.

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