Re: [Xen-devel] OSSTEST: Re-blessing cubietruck-{picasso, gleizes, metzinger} for production use

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("Re: [Xen-devel] OSSTEST: Re-blessing cubietruck-{picasso, 
gleizes, metzinger} for production use"):
> The host console has:
> 
> Jan 18 19:39:57.747858 [ 2354.661150] device vif1.0 entered promiscuous mode
> Jan 18 19:40:10.795484 [ 2354.670132] IPv6: ADDRCONF(NETDEV_UP): vif1.0: link 
> is not ready
> Jan 18 19:40:10.805719 [ 2358.350734] xen-blkback:ring-ref 8, event-channel 
> 3, protocol 1 (arm-abi) persistent grants
> Jan 18 19:40:14.488585 [ 2358.522313] xen-blkback:ring-ref 9, event-channel 
> 4, protocol 1 (arm-abi) persistent grants
> Jan 18 19:40:14.660189 [ 2358.763589] IPv6: ADDRCONF(NETDEV_CHANGE): vif1.0: 
> link becomes ready
> Jan 18 19:40:14.899590 [ 2358.763859] xenbr0: port 2(vif1.0) entered 
> forwarding state
> Jan 18 19:40:14.905182 [ 2358.763933] xenbr0: port 2(vif1.0) entered 
> forwarding state
> Jan 18 19:40:14.910801 (XEN) mm.c:1259:d0v1 gnttab_mark_dirty not implemented 
> yet
> 
> http://osstest.test-lab.xenproject.org/~osstest/pub/logs/78425/test-armhf-armhf-xl-rtds/serial-cubietruck-picasso.log
> 
> So it does appear to be taking nearly 20 to become forwarding.

I don't see where you get that 20s from.  2358-2354 = 4.  Oh wait,
you're looking at the serial log timestamp.  But they disagree with
the kernel's own timestamp.

To me that suggests that the kernel is funted somehow.  The messages
are being generated internally at one time but only actually sent over
the serial port much later.

> I'll add this to my list to investigate further, but I don't think we want
> to tweak the t/o just yet.

Indeed.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel