From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <20190215185151.GG7897@sirena.org.uk> <20190226155948.299aa894a5576e61dda3e5aa@linux-foundation.org> <20190228151438.fc44921e66f2f5d393c8d7b4@linux-foundation.org> <026b5082-32f2-e813-5396-e4a148c813ea@collabora.com> <20190301124100.62a02e2f622ff6b5f178a7c3@linux-foundation.org> <3fafb552-ae75-6f63-453c-0d0e57d818f3@collabora.com> <36faea07-139c-b97d-3585-f7d6d362abc3@collabora.com> <20190306140529.GG3549@rapoport-lnx> <21d138a5-13e4-9e83-d7fe-e0639a8d180a@collabora.com> In-Reply-To: From: "Guenter Roeck" Date: Thu, 11 Apr 2019 13:53:59 -0700 Message-ID: Subject: Re: next/master boot bisection: next-20190215 on beaglebone-black Content-Type: text/plain; charset="UTF-8" List-ID: To: Dan Williams Cc: Kees Cook , kernelci@groups.io, Guillaume Tucker , Mike Rapoport , Andrew Morton , Michal Hocko , Mark Brown , Tomeu Vizoso , Matt Hart , Stephen Rothwell , Kevin Hilman , Enric Balletbo i Serra , Nicholas Piggin , Dominik Brodowski , Masahiro Yamada , Adrian Reber , Linux Kernel Mailing List , Johannes Weiner , Linux MM , Mathieu Desnoyers , Richard Guy Briggs , "Peter Zijlstra (Intel)" , info@kernelci.org On Thu, Apr 11, 2019 at 1:22 PM Dan Williams wrote: > > On Thu, Apr 11, 2019 at 1:08 PM Guenter Roeck wrote: > > > > On Thu, Apr 11, 2019 at 10:35 AM Kees Cook wrote: > > > > > > On Thu, Apr 11, 2019 at 9:42 AM Guenter Roeck wrote: > > > > > > > > On Thu, Apr 11, 2019 at 9:19 AM Kees Cook wrote: > > > > > > > > > > On Thu, Mar 7, 2019 at 7:43 AM Dan Williams wrote: > > > > > > I went ahead and acquired one of these boards to see if I can can > > > > > > debug this locally. > > > > > > > > > > Hi! Any progress on this? Might it be possible to unblock this series > > > > > for v5.2 by adding a temporary "not on ARM" flag? > > > > > > > > > > > > > Can someone send me a pointer to the series in question ? I would like > > > > to run it through my testbed. > > > > > > It's already in -mm and linux-next (",mm: shuffle initial free memory > > > to improve memory-side-cache utilization") but it gets enabled with > > > CONFIG_SHUFFLE_PAGE_ALLOCATOR=y (which was made the default briefly in > > > -mm which triggered problems on ARM as was reverted). > > > > > > > Boot tests report > > > > Qemu test results: > > total: 345 pass: 345 fail: 0 > > > > This is on top of next-20190410 with CONFIG_SHUFFLE_PAGE_ALLOCATOR=y > > and the known crashes fixed. > > In addition to CONFIG_SHUFFLE_PAGE_ALLOCATOR=y you also need the > kernel command line option "page_alloc.shuffle=1" > > ...so I doubt you are running with shuffling enabled. Another way to > double check is: > > cat /sys/module/page_alloc/parameters/shuffle Yes, you are right. Because, with it enabled, I see: Kernel command line: rdinit=/sbin/init page_alloc.shuffle=1 panic=-1 console=ttyAMA0,115200 page_alloc.shuffle=1 ------------[ cut here ]------------ WARNING: CPU: 0 PID: 0 at ./include/linux/jump_label.h:303 page_alloc_shuffle+0x12c/0x1ac static_key_enable(): static key 'page_alloc_shuffle_key+0x0/0x4' used before call to jump_label_init() Modules linked in: CPU: 0 PID: 0 Comm: swapper Not tainted 5.1.0-rc4-next-20190410-00003-g3367c36ce744 #1 Hardware name: ARM Integrator/CP (Device Tree) [] (unwind_backtrace) from [] (show_stack+0x10/0x18) [] (show_stack) from [] (dump_stack+0x18/0x24) [] (dump_stack) from [] (__warn+0xe0/0x108) [] (__warn) from [] (warn_slowpath_fmt+0x44/0x6c) [] (warn_slowpath_fmt) from [] (page_alloc_shuffle+0x12c/0x1ac) [] (page_alloc_shuffle) from [] (shuffle_store+0x28/0x48) [] (shuffle_store) from [] (parse_args+0x1f4/0x350) [] (parse_args) from [] (start_kernel+0x1c0/0x488) [] (start_kernel) from [<00000000>] ( (null)) I'll re-run the test, but I suspect it will drown in warnings. Guenter From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <20190215185151.GG7897@sirena.org.uk> <20190226155948.299aa894a5576e61dda3e5aa@linux-foundation.org> <20190228151438.fc44921e66f2f5d393c8d7b4@linux-foundation.org> <026b5082-32f2-e813-5396-e4a148c813ea@collabora.com> <20190301124100.62a02e2f622ff6b5f178a7c3@linux-foundation.org> <3fafb552-ae75-6f63-453c-0d0e57d818f3@collabora.com> <36faea07-139c-b97d-3585-f7d6d362abc3@collabora.com> <20190306140529.GG3549@rapoport-lnx> <21d138a5-13e4-9e83-d7fe-e0639a8d180a@collabora.com> In-Reply-To: From: "Guenter Roeck" Date: Thu, 11 Apr 2019 13:53:59 -0700 Message-ID: Subject: Re: next/master boot bisection: next-20190215 on beaglebone-black Content-Type: text/plain; charset="UTF-8" List-ID: To: Dan Williams Cc: Kees Cook , kernelci@groups.io, Guillaume Tucker , Mike Rapoport , Andrew Morton , Michal Hocko , Mark Brown , Tomeu Vizoso , Matt Hart , Stephen Rothwell , Kevin Hilman , Enric Balletbo i Serra , Nicholas Piggin , Dominik Brodowski , Masahiro Yamada , Adrian Reber , Linux Kernel Mailing List , Johannes Weiner , Linux MM , Mathieu Desnoyers , Richard Guy Briggs , "Peter Zijlstra (Intel)" , info@kernelci.org On Thu, Apr 11, 2019 at 1:22 PM Dan Williams wrote: > > On Thu, Apr 11, 2019 at 1:08 PM Guenter Roeck wrote: > > > > On Thu, Apr 11, 2019 at 10:35 AM Kees Cook wrote: > > > > > > On Thu, Apr 11, 2019 at 9:42 AM Guenter Roeck wrote: > > > > > > > > On Thu, Apr 11, 2019 at 9:19 AM Kees Cook wrote: > > > > > > > > > > On Thu, Mar 7, 2019 at 7:43 AM Dan Williams wrote: > > > > > > I went ahead and acquired one of these boards to see if I can can > > > > > > debug this locally. > > > > > > > > > > Hi! Any progress on this? Might it be possible to unblock this series > > > > > for v5.2 by adding a temporary "not on ARM" flag? > > > > > > > > > > > > > Can someone send me a pointer to the series in question ? I would like > > > > to run it through my testbed. > > > > > > It's already in -mm and linux-next (",mm: shuffle initial free memory > > > to improve memory-side-cache utilization") but it gets enabled with > > > CONFIG_SHUFFLE_PAGE_ALLOCATOR=y (which was made the default briefly in > > > -mm which triggered problems on ARM as was reverted). > > > > > > > Boot tests report > > > > Qemu test results: > > total: 345 pass: 345 fail: 0 > > > > This is on top of next-20190410 with CONFIG_SHUFFLE_PAGE_ALLOCATOR=y > > and the known crashes fixed. > > In addition to CONFIG_SHUFFLE_PAGE_ALLOCATOR=y you also need the > kernel command line option "page_alloc.shuffle=1" > > ...so I doubt you are running with shuffling enabled. Another way to > double check is: > > cat /sys/module/page_alloc/parameters/shuffle Yes, you are right. Because, with it enabled, I see: Kernel command line: rdinit=/sbin/init page_alloc.shuffle=1 panic=-1 console=ttyAMA0,115200 page_alloc.shuffle=1 ------------[ cut here ]------------ WARNING: CPU: 0 PID: 0 at ./include/linux/jump_label.h:303 page_alloc_shuffle+0x12c/0x1ac static_key_enable(): static key 'page_alloc_shuffle_key+0x0/0x4' used before call to jump_label_init() Modules linked in: CPU: 0 PID: 0 Comm: swapper Not tainted 5.1.0-rc4-next-20190410-00003-g3367c36ce744 #1 Hardware name: ARM Integrator/CP (Device Tree) [] (unwind_backtrace) from [] (show_stack+0x10/0x18) [] (show_stack) from [] (dump_stack+0x18/0x24) [] (dump_stack) from [] (__warn+0xe0/0x108) [] (__warn) from [] (warn_slowpath_fmt+0x44/0x6c) [] (warn_slowpath_fmt) from [] (page_alloc_shuffle+0x12c/0x1ac) [] (page_alloc_shuffle) from [] (shuffle_store+0x28/0x48) [] (shuffle_store) from [] (parse_args+0x1f4/0x350) [] (parse_args) from [] (start_kernel+0x1c0/0x488) [] (start_kernel) from [<00000000>] ( (null)) I'll re-run the test, but I suspect it will drown in warnings. Guenter