From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: next/master boot: 273 boots: 63 failed, 209 passed with 1 untried/unknown (next-20171106) Date: Thu, 9 Nov 2017 14:17:00 +0100 Message-ID: References: <5a0055f1.85a8500a.98d54.a4e4@mx.google.com> <20171106191713.d7jqg2b6zqchythw@sirena.co.uk> <20171107105501.7x74gdqzhr7uulp2@sirena.org.uk> <613bcd63-a215-acbe-9150-c1495f7604f6@collabora.com> <5740b853-4898-2ebc-f67d-0808d1b44c36@nvidia.com> <7cdfa633-d9c6-881a-ae5f-f94f7e6413ee@nvidia.com> <5f064e65-ee29-179b-8102-984d12d24d9d@collabora.com> <15792a16-6b57-a6ad-92dc-0ffaba0354db@nvidia.com> <1eb4e14f-4728-d4f7-95a6-0a6308760d7a@collabora.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <1eb4e14f-4728-d4f7-95a6-0a6308760d7a-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Guillaume Tucker Cc: Jon Hunter , Mark Brown , "open list:TEGRA ARCHITECTURE SUPPORT" , Robin Murphy , "kernelci.org bot" , Linux ARM , Kernel Build Reports Mailman List List-Id: linux-tegra@vger.kernel.org On Thu, Nov 9, 2017 at 1:51 PM, Guillaume Tucker wrote: > On 09/11/17 11:29, Jon Hunter wrote: >> >> >> On 09/11/17 10:43, Guillaume Tucker wrote: >> >> ... >> >>> I actually built these kernel revisions with module support >>> disabled to speed up the builds, and no modules are being >>> downloaded in the LAVA job. >>> >>> If you have a public URL with your known working kernel zImage >>> and dtb, let me know so I could re-run the same test LAVA boot >>> test to see if I get the same results as you (i.e. no hang). >> >> >> I don't have a public URL for the zImage but I can definitely email it >> to you. By the way, when booting I am setting 'init=/bin/bash' so no >> start-up scripts are running. > > > Thanks, I tried your binary and it booted fine. I built > next-20171109 again with and without loadable module support > enabled and it fails with it disabled but passes with it > enabled (even without actually loading any modules): > > * with CONFIG_MODULES disabled (fails): > https://lava.collabora.co.uk/scheduler/job/981215 > > * with plain multi_v7_defconfig and no modules loaded (passes): > https://lava.collabora.co.uk/scheduler/job/981217 > > > So I guess this means disabling loadable modules support has some > interesting side-effects that cause the kernel to crash. I think > the kci builds all leave modules enabled with multi_v7_defconfig, > so the failing boots must be due to something else. Taking > another look at the failing kci boots now... The one thing that comes to mind that happened recently with modules is 371435f78e9e ("kernel debug: support resetting WARN_ONCE for all architectures") Can you try reverting this? It's probably something else, but I'd like to rule it out. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Thu, 9 Nov 2017 14:17:00 +0100 Subject: next/master boot: 273 boots: 63 failed, 209 passed with 1 untried/unknown (next-20171106) In-Reply-To: <1eb4e14f-4728-d4f7-95a6-0a6308760d7a@collabora.com> References: <5a0055f1.85a8500a.98d54.a4e4@mx.google.com> <20171106191713.d7jqg2b6zqchythw@sirena.co.uk> <20171107105501.7x74gdqzhr7uulp2@sirena.org.uk> <613bcd63-a215-acbe-9150-c1495f7604f6@collabora.com> <5740b853-4898-2ebc-f67d-0808d1b44c36@nvidia.com> <7cdfa633-d9c6-881a-ae5f-f94f7e6413ee@nvidia.com> <5f064e65-ee29-179b-8102-984d12d24d9d@collabora.com> <15792a16-6b57-a6ad-92dc-0ffaba0354db@nvidia.com> <1eb4e14f-4728-d4f7-95a6-0a6308760d7a@collabora.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Nov 9, 2017 at 1:51 PM, Guillaume Tucker wrote: > On 09/11/17 11:29, Jon Hunter wrote: >> >> >> On 09/11/17 10:43, Guillaume Tucker wrote: >> >> ... >> >>> I actually built these kernel revisions with module support >>> disabled to speed up the builds, and no modules are being >>> downloaded in the LAVA job. >>> >>> If you have a public URL with your known working kernel zImage >>> and dtb, let me know so I could re-run the same test LAVA boot >>> test to see if I get the same results as you (i.e. no hang). >> >> >> I don't have a public URL for the zImage but I can definitely email it >> to you. By the way, when booting I am setting 'init=/bin/bash' so no >> start-up scripts are running. > > > Thanks, I tried your binary and it booted fine. I built > next-20171109 again with and without loadable module support > enabled and it fails with it disabled but passes with it > enabled (even without actually loading any modules): > > * with CONFIG_MODULES disabled (fails): > https://lava.collabora.co.uk/scheduler/job/981215 > > * with plain multi_v7_defconfig and no modules loaded (passes): > https://lava.collabora.co.uk/scheduler/job/981217 > > > So I guess this means disabling loadable modules support has some > interesting side-effects that cause the kernel to crash. I think > the kci builds all leave modules enabled with multi_v7_defconfig, > so the failing boots must be due to something else. Taking > another look at the failing kci boots now... The one thing that comes to mind that happened recently with modules is 371435f78e9e ("kernel debug: support resetting WARN_ONCE for all architectures") Can you try reverting this? It's probably something else, but I'd like to rule it out. Arnd