From: Ian Campbell <ian.campbell@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Subject: Re: [linux-3.4 test] 64297: regressions - FAIL
Date: Tue, 17 Nov 2015 12:03:35 +0000 [thread overview]
Message-ID: <1447761815.301.37.camel@citrix.com> (raw)
In-Reply-To: <osstest-64297-mainreport@xen.org>
On Mon, 2015-11-16 at 12:06 +0000, osstest service owner wrote:
> flight 64297 linux-3.4 real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/64297/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-i386-xl-qemuu-debianhvm-amd64 6 xen-boot fail REGR. vs. 62277
baroque0
> test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 6 xen-boot fail REGR. vs. 62277
baroque0
> test-amd64-i386-rumpuserxen-i386 6 xen-boot fail REGR. vs. 62277
baroque0
> test-amd64-i386-qemuu-rhel6hvm-intel 6 xen-boot fail REGR. vs. 62277
baroque0
(getting a bit bored now ;-)
> test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm 6 xen-boot fail REGR. vs. 62277
baroque1 (woo!)
> test-amd64-i386-freebsd10-amd64 6 xen-boot fail REGR. vs. 62277
baroque1
> test-amd64-i386-qemut-rhel6hvm-intel 6 xen-boot fail REGR. vs. 62277
baroque1
> test-amd64-i386-xl 6 xen-boot fail REGR. vs. 62277
> test-amd64-i386-xl-qemuu-ovmf-amd64 6 xen-boot fail REGR. vs. 62277
> test-amd64-amd64-xl-multivcpu 6 xen-boot fail REGR. vs. 62277
> test-amd64-amd64-xl-qemuu-ovmf-amd64 6 xen-boot fail REGR. vs. 62277
> test-amd64-i386-xl-qemut-debianhvm-amd64 6 xen-boot fail REGR. vs. 62277
> test-amd64-amd64-xl-qemuu-debianhvm-amd64 6 xen-boot fail REGR. vs. 62277
> test-amd64-amd64-xl-xsm 6 xen-boot fail REGR. vs. 62277
> test-amd64-amd64-xl-qemut-winxpsp3 6 xen-boot fail REGR. vs. 62277
> test-amd64-i386-xl-qemuu-winxpsp3 6 xen-boot fail REGR. vs. 62277
Lets just assume these are all baroque*
From:
http://logs.test-lab.xenproject.org/osstest/results/host/baroque0.html
http://logs.test-lab.xenproject.org/osstest/results/host/baroque1.html
it is pretty clear that baroque* have a problem with booting Linux 3.4. I can see jobs which have passed xen-boot on Linux 3.10 onwards.
In:
http://logs.test-lab.xenproject.org/osstest/logs/64297/test-amd64-i386-qemut-rhel6hvm-intel/serial-baroque1.log
Nov 16 05:07:47.093012 Configuring network interfaces...interface eth0 does not exist!
[...]
Nov 16 05:09:09.117011 Starting web server: apache2apache2: apr_sockaddr_info_get() failed for baroque1
Nov 16 05:09:49.345119 apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Nov 16 05:09:49.353021 .
And no sign of a network device.
In a flight with a newer kernel I see:
http://logs.test-lab.xenproject.org/osstest/logs/64435/test-amd64-i386-qemut-rhel6hvm-intel/serial-baroque0.log
Nov 17 04:12:13.113030 [ 4.292477] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.0.5-k
Nov 17 04:12:13.121018 [ 4.292486] igb: Copyright (c) 2007-2013 Intel Corporation.
Nov 17 04:12:13.129030 [ 4.292587] Already setup the GSI :17
Nov 17 04:12:13.129063 [ 4.320655] igb 0000:02:00.0: added PHC on eth0
Nov 17 04:12:13.137036 [ 4.320659] igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
Nov 17 04:12:13.145028 [ 4.320662] igb 0000:02:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 00:1e:67:af:e4:34
Nov 17 04:12:13.153112 [ 4.320706] igb 0000:02:00.0: eth0: PBA No: 102100-000
Nov 17 04:12:13.161188 [ 4.320709] igb 0000:02:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
Nov 17 04:12:13.169206 [ 4.320779] Already setup the GSI :18
Nov 17 04:12:13.169238 [ 4.347944] igb 0000:03:00.0: added PHC on eth1
Nov 17 04:12:13.177019 [ 4.347947] igb 0000:03:00.0: Intel(R) Gigabit Ethernet Network Connection
Nov 17 04:12:13.185021 [ 4.347950] igb 0000:03:00.0: eth1: (PCIe:2.5Gb/s:Width x1) 00:1e:67:af:e4:35
Nov 17 04:12:13.193025 [ 4.347994] igb 0000:03:00.0: eth1: PBA No: 102100-000
Nov 17 04:12:13.201014 [ 4.347996] igb 0000:03:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
And in
http://logs.test-lab.xenproject.org/osstest/logs/64435/test-amd64-i386-qemut-rhel6hvm-intel/baroque0-output-lspci_-vvv
02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
Which is the same device as Huxelrebe* has (according to <1441877560.24450.365.camel@citrix.com>)
Therefore I think it would be appropriate to set host flag
LinuxKernelMin = 3.5 on Baroque*.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-11-17 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 12:06 [linux-3.4 test] 64297: regressions - FAIL osstest service owner
2015-11-17 12:03 ` Ian Campbell [this message]
2015-11-17 12:09 ` Ian Campbell
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=1447761815.301.37.camel@citrix.com \
--to=ian.campbell@citrix.com \
--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 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.