Re: [Xen-devel] [xen-4.2-testing test] 19031: regressions - FAIL

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Wed, Sep 04, 2013 at 09:12:49AM +0100, Jan Beulich wrote:
> >>> On 04.09.13 at 07:17, xen.org <ian.jackson@xxxxxxxxxxxxx> wrote:
> > flight 19031 xen-4.2-testing real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/19031/ 
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-i386-xend-qemut-winxpsp3  7 windows-install    fail REGR. vs. 
> > 18801
> 
> So the stable trees are apparently using the 3.10-based kernels
> too, and woodlouse is giving a problem there too. Which hints
> even more strongly at a kernel side problem on that specific box
> than a regression in recent -unstable commits. Which in turn
> raises the question of how to best get -unstable's staging tree's
> backlog taken care of, alongside the question of how to get
> pushes on the soon-to-be-released stable trees.

It is interesting that it fails at the same problem the linux-real had
been failing. That is when doing rsync.


5120 bytes (5.1 kB) copied, 0.0194138 s, 264 kB/s
2013-09-04 04:42:13 Z execution took 19 seconds [**>30/2**]: ssh -o 
StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=100 -o 
ServerAliveInterval=100 -o PasswordAuthentication=no -o 
ChallengeResponseAuthentication=no -o 
UserKnownHostsFile=tmp/t.known_hosts_19031.test-amd64-i386-xend-qemut-winxpsp3 
root@xxxxxxxxxxxxx dd if=/dev/zero of=/dev/woodlouse/win.guest.osstest-disk 
count=10
2013-09-04 04:42:13 Z executing rsync ... -p 
/home/xc_osstest/images/winxpsp3.iso 
root@xxxxxxxxxxxxx:/root/19031.test-amd64-i386-xend-qemut-winxpsp3.winxpsp3.iso
2013-09-04 04:58:53 Z command timed out [1000]: rsync -e ssh -o 
StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=100 -o 
ServerAliveInterval=100 -o PasswordAuthentication=no -o 
ChallengeResponseAuthentication=no -o 
UserKnownHostsFile=tmp/t.known_hosts_19031.test-amd64-i386-xend-qemut-winxpsp3 
-p /home/xc_osstest/images/winxpsp3.iso 
root@xxxxxxxxxxxxx:/root/19031.test-amd64-i386-xend-qemut-winxpsp3.winxpsp3.iso
status (timed out) at Osstest/TestSupport.pm line 375.
+ rc=4
+ date -u '+%Y-%m-%d %H:%M:%S Z exit status 4'
2013-09-04 04:58:53 Z exit status 4
+ exit 4
rsync error: unexplained error (code 143) at rsync.c(541) [sender=3.0.3]


Ian, is it possible to a bit more verbose - perhaps that will shed some light
at this awful speed.

There does not seem to be anything about the 'tg3' blowing up?
Ian, would it also be able to get the interrupt count _Before_ and
_after_ the timeout? Perhaps the interrupts aren't going to the
device?

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

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