* [xen-unstable test] 24366: tolerable trouble: broken/fail/pass
@ 2014-01-13 8:19 xen.org
2014-01-13 9:48 ` Ian Campbell
0 siblings, 1 reply; 5+ messages in thread
From: xen.org @ 2014-01-13 8:19 UTC (permalink / raw)
To: xen-devel; +Cc: ian.jackson
flight 24366 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-sedf-pin 14 guest-localmigrate/x10 fail pass in 24364
test-amd64-amd64-xl-winxpsp3 7 windows-install fail pass in 24364
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail like 24364
test-amd64-i386-xend-qemut-winxpsp3 3 host-install(3) broken like 24354
test-amd64-i386-xl-win7-amd64 12 guest-localmigrate/x10 fail like 24354
test-amd64-i386-xl-win7-amd64 7 windows-install fail in 24364 like 24360
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl 9 guest-start fail never pass
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
test-amd64-i386-xl-qemut-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-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop fail never pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail in 24364 never pass
test-amd64-amd64-xl-winxpsp3 13 guest-stop fail in 24364 never pass
version targeted for testing:
xen 4fad2dc72a8607f50c3783e1cbcb3fb25e3af932
baseline version:
xen 4fad2dc72a8607f50c3783e1cbcb3fb25e3af932
jobs:
build-amd64-xend pass
build-i386-xend pass
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-armhf-armhf-xl fail
test-amd64-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-i386-freebsd10-amd64 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-i386-freebsd10-i386 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-amd64-amd64-xl-sedf-pin fail
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-amd64-amd64-xl-sedf fail
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
test-amd64-i386-xl-winxpsp3-vcpus1 fail
test-amd64-i386-xend-qemut-winxpsp3 broken
test-amd64-amd64-xl-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-amd64-i386-xend-winxpsp3 fail
test-amd64-amd64-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
Published tested tree is already up to date.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [xen-unstable test] 24366: tolerable trouble: broken/fail/pass
2014-01-13 8:19 [xen-unstable test] 24366: tolerable trouble: broken/fail/pass xen.org
@ 2014-01-13 9:48 ` Ian Campbell
2014-01-16 14:22 ` Stefano Stabellini
0 siblings, 1 reply; 5+ messages in thread
From: Ian Campbell @ 2014-01-13 9:48 UTC (permalink / raw)
To: xen.org, Stefano Stabellini, Julien Grall; +Cc: xen-devel
On Mon, 2014-01-13 at 08:19 +0000, xen.org wrote:
> flight 24366 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/
> [...]
> Tests which did not succeed, but are not blocking:
> test-armhf-armhf-xl 9 guest-start fail never pass
AKA
http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/test-armhf-armhf-xl/info.html
We are getting there (slowly), the new failure after making EXT4
available is:
http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/test-armhf-armhf-xl/marilith-n5---var-log-xen-console-guest-debian.guest.osstest.log
[ 0.087330] Registering SWP/SWPB emulation handler
[ 0.089780] blkfront: xvda2: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
[ 0.099255] blkfront: xvda1: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
[ 0.179907] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 0.193307] List of all partitions:
[ 0.193325] ca02 4194304 xvda2 driver: vbd
[ 0.193340] ca01 1024000 xvda1 driver: vbd
[ 0.193352] No filesystem could mount root, tried: ext3 ext2 ext4
[ 0.193376] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(202,2)
The disk is on LVM and
http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/test-armhf-armhf-xl/marilith-n5-output-xenstore-ls_-fp
shows that front and backend are in state 4/connected. I don't see any
smoking guns in the logs.
Julien/Stefano -- do you see anything?
The filesystem has been mounted in dom0 (for debootstrap) which is
running the same kernel binary.
The associated kernel build job, including binaries and .config is at
http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/build-amd64-pvops/info.html
and the Xen build is at
http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/build-armhf/info.html
I also have marilith-n4 in a similar state, let me know if you want to
have a poke at it.
In that environment I tried making root be xvda and swap xvdb but that
didn't help. I also tried various rootflags= debug options but no extra
info.
Ian.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [xen-unstable test] 24366: tolerable trouble: broken/fail/pass
2014-01-13 9:48 ` Ian Campbell
@ 2014-01-16 14:22 ` Stefano Stabellini
2014-01-16 14:29 ` Ian Campbell
0 siblings, 1 reply; 5+ messages in thread
From: Stefano Stabellini @ 2014-01-16 14:22 UTC (permalink / raw)
To: Ian Campbell; +Cc: Julien Grall, Stefano Stabellini, xen-devel, xen.org
On Mon, 13 Jan 2014, Ian Campbell wrote:
> On Mon, 2014-01-13 at 08:19 +0000, xen.org wrote:
> > flight 24366 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/
> > [...]
> > Tests which did not succeed, but are not blocking:
> > test-armhf-armhf-xl 9 guest-start fail never pass
> AKA
> http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/test-armhf-armhf-xl/info.html
>
> We are getting there (slowly), the new failure after making EXT4
> available is:
> http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/test-armhf-armhf-xl/marilith-n5---var-log-xen-console-guest-debian.guest.osstest.log
> [ 0.087330] Registering SWP/SWPB emulation handler
> [ 0.089780] blkfront: xvda2: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
> [ 0.099255] blkfront: xvda1: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
> [ 0.179907] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> [ 0.193307] List of all partitions:
> [ 0.193325] ca02 4194304 xvda2 driver: vbd
> [ 0.193340] ca01 1024000 xvda1 driver: vbd
> [ 0.193352] No filesystem could mount root, tried: ext3 ext2 ext4
> [ 0.193376] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(202,2)
>
> The disk is on LVM and
> http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/test-armhf-armhf-xl/marilith-n5-output-xenstore-ls_-fp
> shows that front and backend are in state 4/connected. I don't see any
> smoking guns in the logs.
>
> Julien/Stefano -- do you see anything?
LVM works for me, but I am not using udev at the moment.
> The filesystem has been mounted in dom0 (for debootstrap) which is
> running the same kernel binary.
>
> The associated kernel build job, including binaries and .config is at
> http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/build-amd64-pvops/info.html
> and the Xen build is at
> http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/build-armhf/info.html
>
> I also have marilith-n4 in a similar state, let me know if you want to
> have a poke at it.
>
> In that environment I tried making root be xvda and swap xvdb but that
> didn't help. I also tried various rootflags= debug options but no extra
> info.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xen-unstable test] 24366: tolerable trouble: broken/fail/pass
2014-01-16 14:22 ` Stefano Stabellini
@ 2014-01-16 14:29 ` Ian Campbell
2014-01-21 10:00 ` Ian Campbell
0 siblings, 1 reply; 5+ messages in thread
From: Ian Campbell @ 2014-01-16 14:29 UTC (permalink / raw)
To: Stefano Stabellini; +Cc: Julien Grall, Stefano Stabellini, xen-devel, xen.org
On Thu, 2014-01-16 at 14:22 +0000, Stefano Stabellini wrote:
> On Mon, 13 Jan 2014, Ian Campbell wrote:
> > On Mon, 2014-01-13 at 08:19 +0000, xen.org wrote:
> > > flight 24366 xen-unstable real [real]
> > > http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/
> > > [...]
> > > Tests which did not succeed, but are not blocking:
> > > test-armhf-armhf-xl 9 guest-start fail never pass
> > AKA
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/test-armhf-armhf-xl/info.html
> >
> > We are getting there (slowly), the new failure after making EXT4
> > available is:
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/test-armhf-armhf-xl/marilith-n5---var-log-xen-console-guest-debian.guest.osstest.log
> > [ 0.087330] Registering SWP/SWPB emulation handler
> > [ 0.089780] blkfront: xvda2: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
> > [ 0.099255] blkfront: xvda1: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
> > [ 0.179907] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> > [ 0.193307] List of all partitions:
> > [ 0.193325] ca02 4194304 xvda2 driver: vbd
> > [ 0.193340] ca01 1024000 xvda1 driver: vbd
> > [ 0.193352] No filesystem could mount root, tried: ext3 ext2 ext4
> > [ 0.193376] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(202,2)
> >
> > The disk is on LVM and
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/24366/test-armhf-armhf-xl/marilith-n5-output-xenstore-ls_-fp
> > shows that front and backend are in state 4/connected. I don't see any
> > smoking guns in the logs.
> >
> > Julien/Stefano -- do you see anything?
>
> LVM works for me, but I am not using udev at the moment.
I instrumented the guest f/s and blkfront and it seems like reads are
returning buffers full of 0xc2c2c2c2, which is the pattern that Xen
scrubs pages with in a debug build.
So either there is a cache coherency issue or perhaps something to do
with the dom0 swiotlb doing direct i/o to guest pages and sending them
to the wrong place.
Ian.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xen-unstable test] 24366: tolerable trouble: broken/fail/pass
2014-01-16 14:29 ` Ian Campbell
@ 2014-01-21 10:00 ` Ian Campbell
0 siblings, 0 replies; 5+ messages in thread
From: Ian Campbell @ 2014-01-21 10:00 UTC (permalink / raw)
To: Stefano Stabellini; +Cc: Julien Grall, xen.org, xen-devel, Stefano Stabellini
On Thu, 2014-01-16 at 14:29 +0000, Ian Campbell wrote:
> On Thu, 2014-01-16 at 14:22 +0000, Stefano Stabellini wrote:
> > LVM works for me, but I am not using udev at the moment.
>
> I instrumented the guest f/s and blkfront and it seems like reads are
> returning buffers full of 0xc2c2c2c2, which is the pattern that Xen
> scrubs pages with in a debug build.
>
> So either there is a cache coherency issue or perhaps something to do
> with the dom0 swiotlb doing direct i/o to guest pages and sending them
> to the wrong place.
Just to close this off -- the issue here turned out to be truncation of
dma addresses from 64-bits to 32-bits when LPAE is not enabled. Fixed by
my Linux patch "xen: swiotlb: handle sizeof(dma_addr_t) !=
sizeof(phys_addr_t)".
Ian.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-01-21 10:00 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-13 8:19 [xen-unstable test] 24366: tolerable trouble: broken/fail/pass xen.org
2014-01-13 9:48 ` Ian Campbell
2014-01-16 14:22 ` Stefano Stabellini
2014-01-16 14:29 ` Ian Campbell
2014-01-21 10:00 ` Ian Campbell
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.