From: Platform Team regression test user <osstest@osstest.xs.citrite.net>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [linux-arm-xen baseline-only test] 38131: tolerable FAIL
Date: Wed, 7 Oct 2015 18:18:54 +0100 [thread overview]
Message-ID: <osstest-38131-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 38131 linux-arm-xen real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38131/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-qcow2 9 debian-di-install fail never pass
test-armhf-armhf-xl-vhd 9 debian-di-install fail never pass
test-armhf-armhf-xl-qcow2 9 debian-di-install fail never pass
test-armhf-armhf-xl-raw 9 debian-di-install fail never pass
test-armhf-armhf-libvirt-vhd 9 debian-di-install fail never pass
test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass
test-armhf-armhf-libvirt-xsm 14 guest-saverestore fail never pass
test-armhf-armhf-libvirt 14 guest-saverestore fail never pass
test-armhf-armhf-libvirt 12 migrate-support-check fail never pass
test-armhf-armhf-libvirt-raw 9 debian-di-install fail never pass
test-armhf-armhf-xl 13 saverestore-support-check fail never pass
test-armhf-armhf-xl 12 migrate-support-check fail never pass
test-armhf-armhf-xl-midway 12 migrate-support-check fail never pass
test-armhf-armhf-xl-midway 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-xsm 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-xsm 12 migrate-support-check fail never pass
test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass
test-armhf-armhf-xl-credit2 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-multivcpu 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass
test-armhf-armhf-xl-rtds 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-rtds 12 migrate-support-check fail never pass
version targeted for testing:
linux 9550fff2bd1f88405dd61d86e90807046a580d6c
baseline version:
linux 64972ceb0b0cafc91a09764bc731e1b7f0503b5c
Last test of basis 37825 2015-08-12 14:58:00 Z 56 days
Testing same since 38131 2015-10-06 21:34:13 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
David S. Miller <davem@davemloft.net>
Michel Stam <m.stam@fugro.nl>
Riku Voipio <riku.voipio@linaro.org>
jobs:
build-armhf-xsm pass
build-armhf pass
build-armhf-libvirt pass
build-armhf-pvops pass
test-armhf-armhf-xl pass
test-armhf-armhf-libvirt-xsm fail
test-armhf-armhf-xl-xsm pass
test-armhf-armhf-xl-credit2 pass
test-armhf-armhf-libvirt fail
test-armhf-armhf-xl-midway pass
test-armhf-armhf-xl-multivcpu pass
test-armhf-armhf-libvirt-qcow2 fail
test-armhf-armhf-xl-qcow2 fail
test-armhf-armhf-libvirt-raw fail
test-armhf-armhf-xl-raw fail
test-armhf-armhf-xl-rtds pass
test-armhf-armhf-libvirt-vhd fail
test-armhf-armhf-xl-vhd fail
------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images
Logs, config files, etc. are available at
http://osstest.xs.citrite.net/~osstest/testlogs/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Push not applicable.
------------------------------------------------------------
commit 9550fff2bd1f88405dd61d86e90807046a580d6c
Author: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Date: Thu Nov 6 15:49:41 2014 +0000
asix: Do full reset during ax88772_bind
commit 3cc81d85ee01 ("asix: Don't reset PHY on if_up for ASIX 88772")
causes the ethernet on Arndale to no longer function. This appears to
be because the Arndale ethernet requires a full reset before it will
function correctly, however simply reverting the above patch causes
problems with ethtool settings getting reset.
It seems the problem is that the ethernet is not properly reset during
bind, and indeed the code in ax88772_bind that resets the device is a
very small subset of the actual ax88772_reset function. This patch uses
ax88772_reset in place of the existing reset code in ax88772_bind which
removes some code duplication and fixes the ethernet on Arndale.
It is still possible that the original patch causes some issues with
suspend and resume but that seems like a separate issue and I haven't
had a chance to test that yet.
Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Tested-by: Riku Voipio <riku.voipio@linaro.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit 85d069fec4af144a5f98102e702e27a66d759f94
Author: Michel Stam <m.stam@fugro.nl>
Date: Thu Oct 2 10:22:02 2014 +0200
asix: Don't reset PHY on if_up for ASIX 88772
I've noticed every time the interface is set to 'up,', the kernel
reports that the link speed is set to 100 Mbps/Full Duplex, even
when ethtool is used to set autonegotiation to 'off', half
duplex, 10 Mbps.
It can be tested by:
ifconfig eth0 down
ethtool -s eth0 autoneg off speed 10 duplex half
ifconfig eth0 up
Then checking 'dmesg' for the link speed.
Signed-off-by: Michel Stam <m.stam@fugro.nl>
Signed-off-by: David S. Miller <davem@davemloft.net>
reply other threads:[~2015-10-07 17:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=osstest-38131-mainreport@xen.org \
--to=osstest@osstest.xs.citrite.net \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).