diff mbox

[Xen-devel,xen-unstable,test] 26014: trouble: blocked/broken/pass

Message ID 1398596651.19277.114.camel@hastur.hellion.org.uk
State New
Headers show

Commit Message

Ian Campbell April 27, 2014, 11:04 a.m. UTC 
On Sun, 2014-04-27 at 10:10 +0100, Ian Campbell wrote:
> On Sat, 2014-04-26 at 22:43 +0100, xen.org wrote:
> > flight 26014 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/26014/
> > 
> > Failures and problems with tests :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  build-i386-oldkern            2 host-install(2)         broken REGR. vs. 25954
> >  build-amd64-pvops             2 host-install(2)         broken REGR. vs. 25954
> >  build-amd64-oldkern           2 host-install(2)         broken REGR. vs. 25954
> >  build-amd64                   2 host-install(2)         broken REGR. vs. 25954
> 
> This is lots of:
>         Apr 26 20:48:16.473123 Partition disks
>         Apr 26 20:48:16.473188 ---------------
>         Apr 26 20:48:16.473226 
>         Apr 26 20:48:16.473256 !! ERROR: Logical Volume Manager not available
>         Apr 26 20:48:16.473307 
>         Apr 26 20:48:16.473337 The current kernel doesn't support the Logical Volume Manager. You may need to 
>         Apr 26 20:48:16.481182 load the lvm-mod module.
>         Apr 26 20:48:16.481226 [Press enter to continue] 
> 
> http://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_3.2.57-3_changelog seems to suggest that the stable kernel has been updated recently (I think a new point release is pending), we have a local copy of the kernel but the modules come from the Debian archive, so perhaps this is just a mismatch. The changelog doesn't seem to indicate an ABI change mismatch and at least some modules must be loading OK to get as far as LVM being the issue. The installer hasn't changed though according to ftp://ftp.debian.org/debian/dists/wheezy/main/installer-amd64/.
> 
> I'm going to run some local tests before I try running
> mg-debian-installer-update.

Local tests showed:
        [ 5608.573389] dm_mod: Unknown symbol dm_kobject_release (err 0)

which I think is due to the kernel update. I've pinged the other Debian
kernel maintainers to see if this is expected but in order to unblock
osstest I've also run:
        for i in amd64 i386 armhf ; do 
            OSSTEST_CONFIG=production-config ./mg-debian-installer-update wheezy $i firmware-bnx2; 
        done
        
(which needed the installation of dctrl-tools and bzip2 onto the osstest
control host) and then pushed the following to the osstest gate:

commit add18b3dcccb2c433bde50cd727eed3176070956
Author: Ian Campbell <ian.campbell@citrix.com>
Date:   Sun Apr 27 12:01:12 2014 +0100

    production-config: Update to newer debian installer snapshot.
    
    Signed-off-by: Ian Campbell <ian.campbell@citrix.com>

Comments

Ian Campbell April 28, 2014, 7:48 a.m. UTC | #1 
On Sun, 2014-04-27 at 12:04 +0100, Ian Campbell wrote:
>     production-config: Update to newer debian installer snapshot.

This fixed the x86 machines but unfortunately the armhf kernel which it
picked up from backports was buggy and failed to load the scsi disk
module with:
[  176.286313] crc_t10dif: Unknown symbol crc_t10dif_generic (err 0)

This has happened with both of the two kernel (3.12 and 3.13) which I've
pulled from backports. It looks like we might need a newer version of
depmod/modprobe et al. This is going to involve some poking to figure
out...

Ian.
diff mbox

Patch

diff --git a/production-config b/production-config
index 364976c..7943abf 100644
--- a/production-config
+++ b/production-config
@@ -68,7 +68,7 @@  TftpPxeDir /
 TftpPxeTemplates %ipaddrhex%/pxelinux.cfg
 
 TftpPxeGroup osstest
-TftpDiVersion 2013-12-12
+TftpDiVersion 2014-04-27
 
 XenUsePath /usr/groups/xencore/systems/bin/xenuse
 XenUseUser osstest