* [xen-4.2-testing test] 19031: regressions - FAIL
@ 2013-09-04 5:17 xen.org
2013-09-04 8:12 ` Jan Beulich
0 siblings, 1 reply; 5+ messages in thread
From: xen.org @ 2013-09-04 5:17 UTC (permalink / raw)
To: xen-devel; +Cc: ian.jackson
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
Tests which did not succeed, but are not blocking:
build-armhf 4 xen-build fail never pass
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop fail never pass
test-i386-i386-xl-qemut-winxpsp3 13 guest-stop fail never pass
test-i386-i386-xl-qemuu-winxpsp3 13 guest-stop fail never pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass
test-i386-i386-xl-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass
version targeted for testing:
xen 9f93027afd796a98d7b92898f4ccc772796a4874
baseline version:
xen 56b2771863b7835faf6fa07290bcacb3a68a8326
------------------------------------------------------------
People who touched revisions under test:
David Scott <dave.scott@eu.citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
John Liu <john.liuqiming@huawei.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf fail
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-amd64-i386-xl pass
test-i386-i386-xl pass
test-amd64-i386-rhel6hvm-amd pass
test-amd64-i386-qemut-rhel6hvm-amd pass
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-amd64-xl-qemut-win7-amd64 fail
test-amd64-i386-xl-qemut-win7-amd64 fail
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-win7-amd64 fail
test-amd64-i386-xl-win7-amd64 fail
test-amd64-i386-xl-credit2 pass
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel pass
test-amd64-i386-qemut-rhel6hvm-intel pass
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-amd64-xl-sedf-pin pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv pass
test-amd64-amd64-xl-sedf pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
test-amd64-i386-xl-winxpsp3-vcpus1 fail
test-amd64-i386-xend-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemut-winxpsp3 fail
test-i386-i386-xl-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-i386-i386-xl-qemuu-winxpsp3 fail
test-amd64-i386-xend-winxpsp3 fail
test-amd64-amd64-xl-winxpsp3 fail
test-i386-i386-xl-winxpsp3 fail
------------------------------------------------------------
sg-report-flight on woking.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images
Logs, config files, etc. are available at
http://www.chiark.greenend.org.uk/~xensrcts/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
commit 9f93027afd796a98d7b92898f4ccc772796a4874
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date: Tue Sep 3 11:55:48 2013 +0100
oxenstored: Protect oxenstored from malicious domains.
add check logic when read from IO ring, and if error happens,
then mark the reading connection as "bad", Unless vm reboot,
oxenstored will not handle message from this connection any more.
xs_ring_stubs.c: add a more strict check on ring reading
connection.ml, domain.ml: add getter and setter for bad flag
process.ml: if exception raised when reading from domain's ring,
mark this domain as "bad"
xenstored.ml: if a domain is marked as "bad", do not handle it.
Signed-off-by: John Liu <john.liuqiming@huawei.com>
Acked-by: David Scott <dave.scott@eu.citrix.com>
(cherry picked from commit 704302ce9404c73cfb687d31adcf67094ab5bb53)
(cherry picked from commit a978634bee4db6c5e0ceeb66adcc5114f3f9bc48)
Conflicts:
tools/ocaml/xenstored/domain.ml
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
(qemu changes not included)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xen-4.2-testing test] 19031: regressions - FAIL
2013-09-04 5:17 [xen-4.2-testing test] 19031: regressions - FAIL xen.org
@ 2013-09-04 8:12 ` Jan Beulich
2013-09-04 14:50 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 5+ messages in thread
From: Jan Beulich @ 2013-09-04 8:12 UTC (permalink / raw)
To: ian.jackson; +Cc: xen-devel
>>> On 04.09.13 at 07:17, xen.org <ian.jackson@eu.citrix.com> 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.
Jan
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xen-4.2-testing test] 19031: regressions - FAIL
2013-09-04 8:12 ` Jan Beulich
@ 2013-09-04 14:50 ` Konrad Rzeszutek Wilk
2013-09-04 15:11 ` Ian Jackson
0 siblings, 1 reply; 5+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-09-04 14:50 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel, ian.jackson
On Wed, Sep 04, 2013 at 09:12:49AM +0100, Jan Beulich wrote:
> >>> On 04.09.13 at 07:17, xen.org <ian.jackson@eu.citrix.com> 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@10.80.248.105 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@10.80.248.105:/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@10.80.248.105:/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@lists.xen.org
> http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xen-4.2-testing test] 19031: regressions - FAIL
2013-09-04 14:50 ` Konrad Rzeszutek Wilk
@ 2013-09-04 15:11 ` Ian Jackson
2013-09-04 18:18 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 5+ messages in thread
From: Ian Jackson @ 2013-09-04 15:11 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel, Jan Beulich
Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [xen-4.2-testing test] 19031: regressions - FAIL"):
> 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@10.80.248.105 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@10.80.248.105:/root/19031.test-amd64-i386-xend-qemut-winxpsp3.winxpsp3.iso
This is obviously badly broken. It's copying a tiny known_hosts file,
and it took 19 seconds.
> Ian, is it possible to a bit more verbose - perhaps that will shed some light
> at this awful speed.
I could add a -v but I'm not sure it will be much more illuminating.
> 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?
Surely that wouldn't produce these symptoms...
Ian.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xen-4.2-testing test] 19031: regressions - FAIL
2013-09-04 15:11 ` Ian Jackson
@ 2013-09-04 18:18 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 5+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-09-04 18:18 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel, Jan Beulich
On Wed, Sep 04, 2013 at 04:11:15PM +0100, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [xen-4.2-testing test] 19031: regressions - FAIL"):
> > 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@10.80.248.105 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@10.80.248.105:/root/19031.test-amd64-i386-xend-qemut-winxpsp3.winxpsp3.iso
>
> This is obviously badly broken. It's copying a tiny known_hosts file,
> and it took 19 seconds.
>
> > Ian, is it possible to a bit more verbose - perhaps that will shed some light
> > at this awful speed.
>
> I could add a -v but I'm not sure it will be much more illuminating.
>
> > 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?
>
> Surely that wouldn't produce these symptoms...
Does this happen _only_ with 32-bit dom0? The theory about /proc/interrupts
is that the tg3 is not using the DMA API properly and the device driver
has submitted commands. The hardware sits there and occassionaly polls
instead of going over the commands quickly. That would explain the
slowness. But that won't explain why it works with 64-bit dom0s unless
there is some truncation of physical addresses.
Perhaps you could build with CONFIG_DEBUG_DMA_API=? Perhaps that will shed
some light on it?
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-09-04 18:19 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-09-04 5:17 [xen-4.2-testing test] 19031: regressions - FAIL xen.org
2013-09-04 8:12 ` Jan Beulich
2013-09-04 14:50 ` Konrad Rzeszutek Wilk
2013-09-04 15:11 ` Ian Jackson
2013-09-04 18:18 ` Konrad Rzeszutek Wilk
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.