From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Michal Hocko <mhocko@kernel.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org,
Michael Holzheu <holzheu@linux.ibm.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [-next 20190118] "kernel BUG at mm/page_alloc.c:3112!"
Date: Fri, 25 Jan 2019 09:03:07 +0100 [thread overview]
Message-ID: <20190125080307.GA3561@osiris> (raw)
In-Reply-To: <20190121163747.GL28934@suse.de>
On Mon, Jan 21, 2019 at 04:37:47PM +0000, Mel Gorman wrote:
> On Mon, Jan 21, 2019 at 05:06:07PM +0100, Michal Hocko wrote:
> > This sounds familiar. Cc Mel and Vlastimil.
> >
>
> There is a series sitting in Andrew's inbox that replaces a compaction
> series. A patch is dropped in the new version that deals with pages
> getting freed during compaction that *may* be allowing active pages to
> reach the free list and not tripping a warning like it should. I'm hoping
> it'll be picked up soon to see if this particular bug persists or if it's
> something else.
Has this been picked up already? With linux next 20190124 I still get this:
[ 2529.576230] kernel BUG at mm/page_alloc.c:3112!
[ 2529.576263] illegal operation: 0001 ilc:1 [#1] SMP
[ 2529.576265] Modules linked in: loop kvm xt_tcpudp ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ip6table_nat nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat_ipv4 nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nfnetlink ip6table_filter ip6_tables iptable_filter ip_tables x_tables pkey zcrypt s390_trng rng_core ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha1_s390 sch_fq_codel sha256_s390 sha_common autofs4
[ 2529.576287] CPU: 5 PID: 57 Comm: kcompactd0 Not tainted 5.0.0-20190125.rc3.git0.755d01d17697.300.fc29.s390x+next #1
[ 2529.576289] Hardware name: IBM 3906 M04 704 (z/VM 6.4.0)
[ 2529.576292] Krnl PSW : 0404d00180000000 00000000002bf5d2 (__isolate_free_page+0x212/0x218)
[ 2529.576302] R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3
[ 2529.576310] Krnl GPRS: 0000000000142c00 000003e0f0000080 000003d084cb2400 00000000f0000000
[ 2529.576312] 000003d084cb2408 00000000000002d8 0000000000000007 000003d084cb2400
[ 2529.576312] 0000000000000007 000000017fbfe8c0 000003d000000000 000003d000000007
[ 2529.576313] 000003e001453dc0 000000000014a800 000003e001453ae0 000003e001453a80
[ 2529.576323] Krnl Code: 00000000002bf5c4: f0a8000407fe srp 4(11,%r0),2046,8
00000000002bf5ca: 47000700 bc 0,1792
#00000000002bf5ce: a7f40001 brc 15,2bf5d0
>00000000002bf5d2: 0707 bcr 0,%r7
00000000002bf5d4: 0707 bcr 0,%r7
00000000002bf5d6: 0707 bcr 0,%r7
00000000002bf5d8: c00400000000 brcl 0,2bf5d8
00000000002bf5de: eb6ff0480024 stmg %r6,%r15,72(%r15)
[ 2529.576333] Call Trace:
[ 2529.576335] ([<000003d084cde000>] 0x3d084cde000)
[ 2529.576339] [<00000000002f0fd4>] compaction_alloc+0x394/0x9c8
[ 2529.576344] [<000000000034387e>] migrate_pages+0x1ce/0xaf0
[ 2529.576385] [<00000000002f2e00>] compact_zone+0x620/0xf20
[ 2529.576388] [<00000000002f3a60>] kcompactd_do_work+0x130/0x268
[ 2529.576389] [<00000000002f3c30>] kcompactd+0x98/0x1d0
[ 2529.576393] [<0000000000168500>] kthread+0x140/0x160
[ 2529.576397] [<0000000000a913c6>] kernel_thread_starter+0x6/0x10
[ 2529.576398] [<0000000000a913c0>] kernel_thread_starter+0x0/0x10
[ 2529.576400] Last Breaking-Event-Address:
[ 2529.576402] [<00000000002bf5ce>] __isolate_free_page+0x20e/0x218
[ 2529.576408] Kernel panic - not syncing: Fatal exception: panic_on_oops
next prev parent reply other threads:[~2019-01-25 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 15:43 [-next 20190118] "kernel BUG at mm/page_alloc.c:3112!" Heiko Carstens
2019-01-21 16:06 ` Michal Hocko
2019-01-21 16:37 ` Mel Gorman
2019-01-25 8:03 ` Heiko Carstens [this message]
2019-01-25 8:44 ` Mel Gorman
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=20190125080307.GA3561@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=holzheu@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--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.