From: Guenter Roeck <linux@roeck-us.net>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: Crashes in -next due to 'mm, page_alloc: remove fair zone allocation policy'
Date: Fri, 24 Jun 2016 06:40:03 -0700 [thread overview]
Message-ID: <576D3833.7020608@roeck-us.net> (raw)
In-Reply-To: <20160624083914.GD1868@techsingularity.net>
Hi Mel,
On 06/24/2016 01:39 AM, Mel Gorman wrote:
> On Thu, Jun 23, 2016 at 11:05:33PM -0700, Guenter Roeck wrote:
>> Hi,
>>
>> I see a lot of crashes with various architectures in next-20160623.
>> I bisected mips and sh; both bisect log point to the same patch.
>> Bisect log is attached. arm, ppc, and x86 images crash as well,
>> but I did not confirm if the same patch is the culprit there.
>>
>
> The series has been dropped. Due to conflicts with other patches, there
> were a few bugs introduced, one which potentially corrupted memory. Just
> to be sure though, what sort of workload crashed just in case I need to
> adjust the test coverage?
>
This is just a basic qemu boot test. No workload at all.
Here is a complete list of failures.
Qemu test results:
total: 107 pass: 66 fail: 41
Failed tests:
arm:versatilepb-scsi:versatile_defconfig:versatile-pb
arm:versatileab:versatile_defconfig:versatile-ab
arm:versatilepb:versatile_defconfig:versatile-pb
arm:imx25-pdk:imx_v4_v5_defconfig:imx25-pdk
arm:midway:multi_v7_defconfig:ecx-2000
arm:realview-pb-a8:realview_defconfig
arm:akita:spitz_defconfig
arm:spitz:spitz_defconfig
arm:akita:pxa_defconfig
arm:borzoi:pxa_defconfig
arm:mainstone:pxa_defconfig
arm:spitz:pxa_defconfig
arm:terrier:pxa_defconfig
arm:tosa:pxa_defconfig
arm:z2:pxa_defconfig
arm:collie:collie_defconfig
arm:integratorcp:integrator_defconfig:integratorcp
mips:malta_defconfig:nosmp
mips64:malta_defconfig:nosmp
mipsel64:fuloong2e_defconfig:fulong2e
powerpc:mac99:nosmp:ppc_book3s_defconfig
powerpc:g3beige:nosmp:ppc_book3s_defconfig
powerpc:virtex-ml507:44x/virtex5_defconfig
powerpc:mpc8548cds:85xx/mpc85xx_cds_defconfig
powerpc:bamboo:44x/bamboo_defconfig
powerpc:nosmp:ppc64_book3s_defconfig
sh:rts7751r2dplus_defconfig
x86:core2duo:q35:x86_pc_nosmp_defconfig
x86:Conroe:isapc:x86_pc_nosmp_defconfig
x86:Opteron_G1:pc:x86_pc_nosmp_defconfig
x86:n270:isapc:x86_pc_nosmp_defconfig
x86_64:SandyBridge:q35:x86_64_pc_defconfig
x86_64:Haswell:q35:x86_64_pc_defconfig
x86_64:core2duo:pc:x86_64_pc_defconfig
x86_64:Nehalem:q35:x86_64_pc_defconfig
x86_64:phenom:pc:x86_64_pc_defconfig
x86_64:Opteron_G1:q35:x86_64_pc_defconfig
x86_64:Opteron_G4:pc:x86_64_pc_nosmp_defconfig
x86_64:IvyBridge:q35:x86_64_pc_nosmp_defconfig
xtensa:dc233c:ml605:generic_kc705_defconfig
xtensa:dc233c:kc705:generic_kc705_defconfig
For logs, please see the next column of the qemu test results at
http://kerneltests.org/builders. You might have to dive into individual builds
if you check after a more recent -next kernel has been made available and your
changes were dropped in that kernel. Test results are available for about
a month.
Build and test scripts are available at https://github.com/groeck/linux-build-test.
Hope this helps,
Guenter
next prev parent reply other threads:[~2016-06-24 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 6:05 Crashes in -next due to 'mm, page_alloc: remove fair zone allocation policy' Guenter Roeck
2016-06-24 8:39 ` Mel Gorman
2016-06-24 13:40 ` Guenter Roeck [this message]
2016-06-24 15:50 ` Mel Gorman
2016-06-24 16:46 ` Guenter Roeck
2016-06-24 18:13 ` Mel Gorman
2016-06-24 20:15 ` Guenter Roeck
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=576D3833.7020608@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=vbabka@suse.cz \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox