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: Crashes in -next due to 'mm, page_alloc: remove fair zone allocation policy'
Date: Thu, 23 Jun 2016 23:05:33 -0700 [thread overview]
Message-ID: <20160624060533.GA9507@roeck-us.net> (raw)
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.
I tried to revert the patch, but that did not work due to subsequent patches
affecting the same code.
Guenter
---
# bad: [5c4d1ca9cfa71d9515ce5946cfc6497d22b1108e] Add linux-next specific files for 20160623
# good: [33688abb2802ff3a230bd2441f765477b94cc89e] Linux 4.7-rc4
git bisect start 'HEAD' 'v4.7-rc4'
# good: [0cc6a3a989f351112e1b8534f787b19a125b6281] Merge remote-tracking branch 'drm/drm-next'
git bisect good 0cc6a3a989f351112e1b8534f787b19a125b6281
# good: [72e9d226a2de83374fc66e59955a4d34c34c0c0f] Merge remote-tracking branch 'clockevents/clockevents/next'
git bisect good 72e9d226a2de83374fc66e59955a4d34c34c0c0f
# good: [0d35ad6e1a47d9951249542c90038039730f2cc4] Merge remote-tracking branch 'staging/staging-next'
git bisect good 0d35ad6e1a47d9951249542c90038039730f2cc4
# good: [9b5c3f08e656e53b226c4763a111c85675b1e651] Merge remote-tracking branch 'coresight/next'
git bisect good 9b5c3f08e656e53b226c4763a111c85675b1e651
# good: [760dfb53d9c2a81ef36895a12f7cabdb69cabf54] shmem, thp: respect MADV_{NO,}HUGEPAGE for file mappings
git bisect good 760dfb53d9c2a81ef36895a12f7cabdb69cabf54
# bad: [d664b7e1455775b014abafcf85134573c496e2ef] samples/kprobe: convert the printk to pr_info/pr_err
git bisect bad d664b7e1455775b014abafcf85134573c496e2ef
# good: [692ac72dc26d4735abefdba0876049710d1e57f8] mm, vmscan: add classzone information to tracepoints
git bisect good 692ac72dc26d4735abefdba0876049710d1e57f8
# bad: [78aa21d400775ad5d6df41209369430114c7f56a] proc_oom_score: remove tasklist_lock and pid_alive()
git bisect bad 78aa21d400775ad5d6df41209369430114c7f56a
# bad: [e7a21d36c970ce6506dfbde2e34d773ff492280a] mm, oom_adj: make sure processes sharing mm have same view of oom_score_adj
git bisect bad e7a21d36c970ce6506dfbde2e34d773ff492280a
# bad: [9c22c0aef92a9dd9cead68e4796bb09253a3efb6] thp: fix comments of __pmd_trans_huge_lock()
git bisect bad 9c22c0aef92a9dd9cead68e4796bb09253a3efb6
# bad: [76a3308aea2ccb472eeebdf78dd27590b8ee8541] mm: page_alloc: cache the last node whose dirty limit is reached
git bisect bad 76a3308aea2ccb472eeebdf78dd27590b8ee8541
# bad: [089fcc128177aaa80935ad21d522a5be11007f9c] mm, page_alloc: remove fair zone allocation policy
git bisect bad 089fcc128177aaa80935ad21d522a5be11007f9c
# first bad commit: [089fcc128177aaa80935ad21d522a5be11007f9c] mm, page_alloc: remove fair zone allocation policy
next reply other threads:[~2016-06-24 6:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 6:05 Guenter Roeck [this message]
2016-06-24 8:39 ` Crashes in -next due to 'mm, page_alloc: remove fair zone allocation policy' Mel Gorman
2016-06-24 13:40 ` Guenter Roeck
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=20160624060533.GA9507@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 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.