From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 11 Apr 2019 23:49:46 +0300 From: Mike Rapoport Subject: Re: next/master boot bisection: next-20190215 on beaglebone-black References: <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> MIME-Version: 1.0 In-Reply-To: Message-Id: <20190411204945.GA26085@rapoport-lnx> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-ID: To: Guenter Roeck Cc: Kees Cook , kernelci@groups.io, Dan Williams , Guillaume Tucker , 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 01:08:15PM -0700, 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. > > $ git log --oneline next-20190410.. > 3367c36ce744 Set SHUFFLE_PAGE_ALLOCATOR=y for testing. > d2aee8b3cd5d Revert "crypto: scompress - Use per-CPU struct instead > multiple variables" > 4bc9f5bc9a84 Fix: rhashtable: use bit_spin_locks to protect hash bucket. > > Boot tests on arm are: > > Building arm:versatilepb:versatile_defconfig:aeabi:pci:scsi:mem128:versatile-pb:rootfs > ... running ........ passed > Building arm:versatilepb:versatile_defconfig:aeabi:pci:mem128:versatile-pb:initrd > ... running ........ passed ... > Building arm:witherspoon-bmc:aspeed_g5_defconfig:notests:aspeed-bmc-opp-witherspoon:initrd > ... running ........... passed > Building arm:ast2500-evb:aspeed_g5_defconfig:notests:aspeed-ast2500-evb:initrd > ... running ................ passed > Building arm:romulus-bmc:aspeed_g5_defconfig:notests:aspeed-bmc-opp-romulus:initrd > ... running ......................... passed > Building arm:mps2-an385:mps2_defconfig:mps2-an385:initrd ... running > ...... passed The issue was with an omap2 board and, AFAIK, qemu does not simulate those. -- Sincerely yours, Mike.