From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Date: Mon, 08 Dec 2014 16:45:00 +0000 Subject: Re: stable boot: 93 boots: 92 pass, 1 fail (v3.17.6) Message-Id: <7htx16um43.fsf@deeprootsystems.com> List-Id: References: <2553650.3KSUKtTdo3@wuerfel> In-Reply-To: <2553650.3KSUKtTdo3@wuerfel> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-sh@vger.kernel.org Arnd Bergmann writes: > On Monday 08 December 2014 14:48:20 Geert Uytterhoeven wrote: >> On Mon, Dec 8, 2014 at 12:35 PM, Arnd Bergmann wrote: >> > On Sunday 07 December 2014 21:49:05 Kevin's boot bot wrote: >> >> Full Build report: http://status.armcloud.us/build/stable/kernel/v3.17.6/ >> >> Full Boot report: http://status.armcloud.us/boot/all/job/stable/kernel/v3.17.6/ >> >> >> >> Tree/Branch: stable >> >> Git describe: v3.17.6 >> >> >> >> Failed boot tests >> >> ========>> >> emev2-kzm9d: FAIL: arm-shmobile_defconfig >> >> http://storage.armcloud.us/kernel-ci/stable/v3.17.6/arm-shmobile_defconfig/boot-emev2-kzm9d.html >> >> >> > >> > I tried to look at the reports, but the links don't work. Going >> > back in the archive, I see that it was still working until v3.17.2, >> > broken in v3.17.4/.5/.6 and the boot report for v3.17.3 seemed to run >> > into an unrelated issue. Mainline was always fine since 3.17, only >> > the stable kernels had problems: >> > >> > http://storage.armcloud.us/kernel-ci/stable/v3.17.2/arm-shmobile_defconfig/boot-emev2-kzm9d.html >> > http://storage.armcloud.us/kernel-ci/stable/v3.17.3/arm-shmobile_defconfig/boot-emev2-kzm9d.html >> > http://storage.armcloud.us/kernel-ci/stable/v3.17.4/arm-shmobile_defconfig/boot-emev2-kzm9d.html >> > >> > It may be worth having the sh team investigate the problem some more, >> > to see if a bad patch made it into stable kernels. >> >> Thanks for telling us! >> >> I don't have a kzm9d, so I'm just guessing based on the evidence. >> >> 1. When comparing successful v3.1.72 with failed v3.17.4, I see: >> >> Sending DHCP requests ., OK >> -IP-Config: Got DHCP answer from 192.168.1.3, my address is 192.168.1.189 >> +IP-Config: Got DHCP answer from 192.168.1.254, my address is 192.168.1.188 >> IP-Config: Complete: >> - device=eth0, hwaddr:01:9b:04:03:cd, ipaddr2.168.1.189, >> mask%5.255.255.0, gw2.168.1.254 >> - host=kzm9d, domain=lan, nis-domain=(none) >> - bootserver2.168.1.2, rootserver2.168.1.2, >> rootpath=/opt/kjh/rootfs/debian/armel,rsize@96,wsize@96 >> - nameserver02.168.1.254, nameserver1f.93.87.2, >> nameserver2!6.231.41.2 >> + device=eth0, hwaddr:01:9b:04:03:cd, ipaddr2.168.1.188, >> mask%5.255.255.0, gw2.168.1.254 >> + host2.168.1.188, domain=lan, nis-domain=(none) >> + bootserver2.168.1.254, rootserver2.168.1.254, rootpath>> + nameserver02.168.1.254 >> ALSA device list: >> No soundcards found. >> >> So both the client and server IP addresses have changed. Is there a proper NFS >> root file system available? Mounting of NFS root will time out, but the boot >> farm management software may time out earlier, so we don't get to see the >> panic message? > > The 3.18-rc7 boot got these: > > IP-Config: Got DHCP answer from 192.168.1.254, my address is 192.168.1.185 > IP-Config: Complete: > device=eth0, hwaddr:01:9b:04:03:cd, ipaddr2.168.1.185, mask%5.255.255.0, gw2.168.1.254 > host2.168.1.185, domain=lan, nis-domain=(none) > bootserver2.168.1.254, rootserver2.168.1.254, rootpath> nameserver02.168.1.254 > > So it's the same server as the failing config, and yet another client > address. I'd say it's unlikely to be related. I figured it out. The problem is that my DHCP is no longer giving out a default root-path, and I neglected to update the commandline for this board. I'd forgotten that the shmobile_defconfig doesn't have initrd support in v3.17, so it can't boot from a ramdisk like all my other boards. Geert, Simon, any objections to enabling initrd support in v3.17 stable? Probably just asking Greg to cherry-pick mainline commit which does this[1] should suffice. Kevin [1] commit 874ee23c83d888f8824305c277e047c7799f30b9 Author: Kevin Hilman Date: Wed Aug 13 17:07:15 2014 -0700 ARM: shmobile: defconfig: enable initrd Enable initrd support. Signed-off-by: Kevin Hilman [horms+renesas@verge.net.au: dropped enabling atag dtb compat] Signed-off-by: Simon Horman 2H