From: Guillaume Tucker <guillaume.tucker@collabora.com> To: Dan Williams <dan.j.williams@intel.com>, Andrew Morton <akpm@linux-foundation.org>, Michal Hocko <mhocko@suse.com> Cc: Mark Brown <broonie@kernel.org>, Tomeu Vizoso <tomeu.vizoso@collabora.com>, Matt Hart <matthew.hart@linaro.org>, Stephen Rothwell <sfr@canb.auug.org.au>, khilman@baylibre.com, enric.balletbo@collabora.com, Nicholas Piggin <npiggin@gmail.com>, Dominik Brodowski <linux@dominikbrodowski.net>, Masahiro Yamada <yamada.masahiro@socionext.com>, Kees Cook <keescook@chromium.org>, Adrian Reber <adrian@lisas.de>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Johannes Weiner <hannes@cmpxchg.org>, Linux MM <linux-mm@kvack.org>, Mathieu Desnoyers <mathieu.desnoyers@efficios.com>, Richard Guy Briggs <rgb@redhat.com>, "Peter Zijlstra (Intel)" <peterz@infradead.org>, info@kernelci.org Subject: Re: next/master boot bisection: next-20190215 on beaglebone-black Date: Fri, 1 Mar 2019 09:25:24 +0100 [thread overview] Message-ID: <026b5082-32f2-e813-5396-e4a148c813ea@collabora.com> (raw) In-Reply-To: <CAPcyv4hDmmK-L=0txw7L9O8YgvAQxZfVFiSoB4LARRnGQ3UC7Q@mail.gmail.com> On 01/03/2019 00:55, Dan Williams wrote: > On Thu, Feb 28, 2019 at 3:14 PM Andrew Morton <akpm@linux-foundation.org> wrote: >> >> On Tue, 26 Feb 2019 16:04:04 -0800 Dan Williams <dan.j.williams@intel.com> wrote: >> >>> On Tue, Feb 26, 2019 at 4:00 PM Andrew Morton <akpm@linux-foundation.org> wrote: >>>> >>>> On Fri, 15 Feb 2019 18:51:51 +0000 Mark Brown <broonie@kernel.org> wrote: >>>> >>>>> On Fri, Feb 15, 2019 at 10:43:25AM -0800, Andrew Morton wrote: >>>>>> On Fri, 15 Feb 2019 10:20:10 -0800 (PST) "kernelci.org bot" <bot@kernelci.org> wrote: >>>>> >>>>>>> Details: https://kernelci.org/boot/id/5c666ea959b514b017fe6017 >>>>>>> Plain log: https://storage.kernelci.org//next/master/next-20190215/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-7/lab-collabora/boot-am335x-boneblack.txt >>>>>>> HTML log: https://storage.kernelci.org//next/master/next-20190215/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-7/lab-collabora/boot-am335x-boneblack.html >>>>> >>>>>> Thanks. >>>>> >>>>>> But what actually went wrong? Kernel doesn't boot? >>>>> >>>>> The linked logs show the kernel dying early in boot before the console >>>>> comes up so yeah. There should be kernel output at the bottom of the >>>>> logs. >>>> >>>> I assume Dan is distracted - I'll keep this patchset on hold until we >>>> can get to the bottom of this. >>> >>> Michal had asked if the free space accounting fix up addressed this >>> boot regression? I was awaiting word on that. >> >> hm, does bot@kernelci.org actually read emails? Let's try info@ as well.. bot@kernelci.org is not person, it's a send-only account for automated reports. So no, it doesn't read emails. I guess the tricky point here is that the authors of the commits found by bisections may not always have the hardware needed to reproduce the problem. So it needs to be dealt with on a case-by-case basis: sometimes they do have the hardware, sometimes someone else on the list or on CC does, and sometimes it's better for the people who have access to the test lab which ran the KernelCI test to deal with it. This case seems to fall into the last category. As I have access to the Collabora lab, I can do some quick checks to confirm whether the proposed patch does fix the issue. I hadn't realised that someone was waiting for this to happen, especially as the BeagleBone Black is a very common platform. Sorry about that, I'll take a look today. It may be a nice feature to be able to give access to the KernelCI test infrastructure to anyone who wants to debug an issue reported by KernelCI or verify a fix, so they won't need to have the hardware locally. Something to think about for the future. >> Is it possible to determine whether this regression is still present in >> current linux-next? I'll try to re-apply the patch that caused the issue, then see if the suggested change fixes it. As far as the current linux-next master branch is concerned, KernelCI boot tests are passing fine on that platform. Guillaume
WARNING: multiple messages have this Message-ID (diff)
From: "Guillaume Tucker" <guillaume.tucker@gmail.com> To: Dan Williams <dan.j.williams@intel.com>, Andrew Morton <akpm@linux-foundation.org>, Michal Hocko <mhocko@suse.com> Cc: Mark Brown <broonie@kernel.org>, Tomeu Vizoso <tomeu.vizoso@collabora.com>, Matt Hart <matthew.hart@linaro.org>, Stephen Rothwell <sfr@canb.auug.org.au>, khilman@baylibre.com, enric.balletbo@collabora.com, Nicholas Piggin <npiggin@gmail.com>, Dominik Brodowski <linux@dominikbrodowski.net>, Masahiro Yamada <yamada.masahiro@socionext.com>, Kees Cook <keescook@chromium.org>, Adrian Reber <adrian@lisas.de>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Johannes Weiner <hannes@cmpxchg.org>, Linux MM <linux-mm@kvack.org>, Mathieu Desnoyers <mathieu.desnoyers@efficios.com>, Richard Guy Briggs <rgb@redhat.com>, "Peter Zijlstra (Intel)" <peterz@infradead.org>, info@kernelci.org Subject: Re: next/master boot bisection: next-20190215 on beaglebone-black Date: Fri, 1 Mar 2019 09:25:24 +0100 [thread overview] Message-ID: <026b5082-32f2-e813-5396-e4a148c813ea@collabora.com> (raw) In-Reply-To: <CAPcyv4hDmmK-L=0txw7L9O8YgvAQxZfVFiSoB4LARRnGQ3UC7Q@mail.gmail.com> On 01/03/2019 00:55, Dan Williams wrote: > On Thu, Feb 28, 2019 at 3:14 PM Andrew Morton <akpm@linux-foundation.org> wrote: >> >> On Tue, 26 Feb 2019 16:04:04 -0800 Dan Williams <dan.j.williams@intel.com> wrote: >> >>> On Tue, Feb 26, 2019 at 4:00 PM Andrew Morton <akpm@linux-foundation.org> wrote: >>>> >>>> On Fri, 15 Feb 2019 18:51:51 +0000 Mark Brown <broonie@kernel.org> wrote: >>>> >>>>> On Fri, Feb 15, 2019 at 10:43:25AM -0800, Andrew Morton wrote: >>>>>> On Fri, 15 Feb 2019 10:20:10 -0800 (PST) "kernelci.org bot" <bot@kernelci.org> wrote: >>>>> >>>>>>> Details: https://kernelci.org/boot/id/5c666ea959b514b017fe6017 >>>>>>> Plain log: https://storage.kernelci.org//next/master/next-20190215/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-7/lab-collabora/boot-am335x-boneblack.txt >>>>>>> HTML log: https://storage.kernelci.org//next/master/next-20190215/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-7/lab-collabora/boot-am335x-boneblack.html >>>>> >>>>>> Thanks. >>>>> >>>>>> But what actually went wrong? Kernel doesn't boot? >>>>> >>>>> The linked logs show the kernel dying early in boot before the console >>>>> comes up so yeah. There should be kernel output at the bottom of the >>>>> logs. >>>> >>>> I assume Dan is distracted - I'll keep this patchset on hold until we >>>> can get to the bottom of this. >>> >>> Michal had asked if the free space accounting fix up addressed this >>> boot regression? I was awaiting word on that. >> >> hm, does bot@kernelci.org actually read emails? Let's try info@ as well.. bot@kernelci.org is not person, it's a send-only account for automated reports. So no, it doesn't read emails. I guess the tricky point here is that the authors of the commits found by bisections may not always have the hardware needed to reproduce the problem. So it needs to be dealt with on a case-by-case basis: sometimes they do have the hardware, sometimes someone else on the list or on CC does, and sometimes it's better for the people who have access to the test lab which ran the KernelCI test to deal with it. This case seems to fall into the last category. As I have access to the Collabora lab, I can do some quick checks to confirm whether the proposed patch does fix the issue. I hadn't realised that someone was waiting for this to happen, especially as the BeagleBone Black is a very common platform. Sorry about that, I'll take a look today. It may be a nice feature to be able to give access to the KernelCI test infrastructure to anyone who wants to debug an issue reported by KernelCI or verify a fix, so they won't need to have the hardware locally. Something to think about for the future. >> Is it possible to determine whether this regression is still present in >> current linux-next? I'll try to re-apply the patch that caused the issue, then see if the suggested change fixes it. As far as the current linux-next master branch is concerned, KernelCI boot tests are passing fine on that platform. Guillaume
next prev parent reply other threads:[~2019-03-01 8:25 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-15 18:20 next/master boot bisection: next-20190215 on beaglebone-black kernelci.org bot 2019-02-15 18:43 ` Andrew Morton 2019-02-15 18:51 ` Mark Brown 2019-02-15 19:00 ` Andrew Morton 2019-02-16 6:21 ` Stephen Rothwell 2019-02-26 23:59 ` Andrew Morton 2019-02-27 0:04 ` Dan Williams 2019-02-27 0:04 ` Dan Williams 2019-02-28 23:14 ` Andrew Morton 2019-02-28 23:55 ` Dan Williams 2019-02-28 23:55 ` Dan Williams 2019-03-01 8:25 ` Guillaume Tucker [this message] 2019-03-01 8:25 ` Guillaume Tucker 2019-03-01 10:40 ` Mike Rapoport 2019-03-01 11:49 ` Mark Brown 2019-03-01 20:41 ` Andrew Morton 2019-03-01 21:04 ` Guillaume Tucker 2019-03-01 21:04 ` Guillaume Tucker 2019-03-01 23:23 ` Dan Williams 2019-03-01 23:23 ` Dan Williams 2019-03-06 10:14 ` Guillaume Tucker 2019-03-06 10:14 ` Guillaume Tucker 2019-03-06 14:05 ` Mike Rapoport 2019-03-07 9:16 ` Guillaume Tucker 2019-03-07 9:16 ` Guillaume Tucker 2019-03-07 15:43 ` Dan Williams 2019-03-07 15:43 ` Dan Williams 2019-04-10 22:52 ` Kees Cook 2019-04-10 22:52 ` Kees Cook 2019-04-11 16:42 ` Guenter Roeck 2019-04-11 16:42 ` Guenter Roeck 2019-04-11 16:42 ` Guenter Roeck 2019-04-11 17:35 ` Kees Cook 2019-04-11 17:35 ` Kees Cook 2019-04-11 20:08 ` Guenter Roeck 2019-04-11 20:08 ` Guenter Roeck 2019-04-11 20:22 ` Dan Williams 2019-04-11 20:22 ` Dan Williams 2019-04-11 20:53 ` Guenter Roeck 2019-04-11 20:53 ` Guenter Roeck 2019-04-16 18:54 ` Dan Williams 2019-04-16 18:54 ` Dan Williams 2019-04-16 19:17 ` Mathieu Desnoyers 2019-04-16 19:17 ` Mathieu Desnoyers 2019-04-16 19:25 ` Mathieu Desnoyers 2019-04-16 19:25 ` Mathieu Desnoyers 2019-04-16 19:45 ` Mathieu Desnoyers 2019-04-16 19:45 ` Mathieu Desnoyers 2019-04-16 19:33 ` Guenter Roeck 2019-04-16 19:33 ` Guenter Roeck 2019-04-16 20:37 ` Dan Williams 2019-04-16 20:37 ` Dan Williams 2019-04-16 21:04 ` Guenter Roeck 2019-04-16 21:04 ` Guenter Roeck 2019-04-17 3:30 ` Kees Cook 2019-04-17 3:30 ` Kees Cook 2019-04-16 20:05 ` Mathieu Desnoyers 2019-04-16 20:05 ` Mathieu Desnoyers 2019-04-11 20:49 ` Mike Rapoport 2019-03-01 11:45 ` Mark Brown 2019-03-01 9:02 ` Vlastimil Babka 2019-02-18 9:44 ` Michal Hocko
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=026b5082-32f2-e813-5396-e4a148c813ea@collabora.com \ --to=guillaume.tucker@collabora.com \ --cc=adrian@lisas.de \ --cc=akpm@linux-foundation.org \ --cc=broonie@kernel.org \ --cc=dan.j.williams@intel.com \ --cc=enric.balletbo@collabora.com \ --cc=hannes@cmpxchg.org \ --cc=info@kernelci.org \ --cc=keescook@chromium.org \ --cc=khilman@baylibre.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux@dominikbrodowski.net \ --cc=mathieu.desnoyers@efficios.com \ --cc=matthew.hart@linaro.org \ --cc=mhocko@suse.com \ --cc=npiggin@gmail.com \ --cc=peterz@infradead.org \ --cc=rgb@redhat.com \ --cc=sfr@canb.auug.org.au \ --cc=tomeu.vizoso@collabora.com \ --cc=yamada.masahiro@socionext.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: linkBe 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.