From: Anshuman Khandual <anshuman.khandual@arm.com>
To: kernel test robot <lkp@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Christophe Leroy <christophe.leroy@c-s.fr>, Qian Cai <cai@lca.pw>,
Catalin Marinas <catalin.marinas@arm.com>,
Ingo Molnar <mingo@kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Vineet Gupta <vgupta@synopsys.com>, Will Deacon <will@kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org
Subject: Re: [mm/debug] fa6726c1e7: kernel_BUG_at_include/linux/mm.h
Date: Tue, 28 Apr 2020 07:18:46 +0530 [thread overview]
Message-ID: <51dcbcbf-6020-6672-05b0-5bb10c6292b5@arm.com> (raw)
In-Reply-To: <20200427140706.GC5770@shao2-debian>
On 04/27/2020 07:37 PM, kernel test robot wrote:
>
> [ 10.263354] kernel BUG at include/linux/mm.h:699!
> [ 10.264320] invalid opcode: 0000 [#1] SMP
> [ 10.264872] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.7.0-rc2-00230-gfa6726c1e7f01 #2
> [ 10.265928] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
> [ 10.267074] EIP: __free_pages+0x4f/0x62
> [ 10.267615] Code: 85 ff 74 0e 89 fa 89 f0 e8 83 ed ff ff 5b 5e 5f 5d c3 89 f0 e8 57 ff ff ff 5b 5e 5f 5d c3 ba fc 86 fc c1 89 f0 e8 ff 2e fe ff <0f> 0b 0f b6 cb ba ff ff ff ff 89 f0 e8 07 8f 01 00 eb bf 55 89 e5
> [ 10.270098] EAX: 0000003e EBX: ee800000 ECX: 00000000 EDX: c0068000
> [ 10.270925] ESI: eece0640 EDI: c016d020 EBP: c0071f10 ESP: c0071f04
> [ 10.271786] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010286
> [ 10.272724] CR0: 80050033 CR2: b7d6467d CR3: 023d0000 CR4: 000006b0
> [ 10.273572] Call Trace:
> [ 10.273912] free_pages+0x3d/0x43
> [ 10.274367] pgd_free+0xea/0x11b
> [ 10.274807] __mmdrop+0x3c/0xc7
> [ 10.275237] ? __free_pages+0x3e/0x62
> [ 10.275761] debug_vm_pgtable+0x411/0x419
> [ 10.276305] ? rest_init+0x23c/0x23c
> [ 10.276767] kernel_init+0x15/0xf4
> [ 10.277208] ? schedule_tail_wrapper+0x9/0xc
> [ 10.277756] ret_from_fork+0x2e/0x38
> [ 10.278217] Modules linked in: stm_p_basic
> [ 10.278776] ---[ end trace b838f89424113a3a ]---
This is an unsupported (enabled via CONFIG_EXPERT) X86 platform (CONFIG_X86_PAE)
and is known to fail. The latest (V17) patch had moved the test invocation into
a late_initcall() per Linus thus pushing down any possible failures (like this)
after early boot. Please ignore this report.
Apart from this X86_PAE based config, no other platform failures have reported
so far. Assuming that this test robot does have a good platform coverage, the
CONFIG_EXPERT method of enabling CONFIG_DEBUG_VM_PGTABLE should help in getting
more platform coverage for this test.
- Anshuman
next prev parent reply other threads:[~2020-04-28 1:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 14:07 kernel test robot
2020-04-28 1:48 ` Anshuman Khandual [this message]
2020-04-28 2:05 ` Qian Cai
2020-04-28 2:35 ` Anshuman Khandual
2020-04-28 2:51 ` Qian Cai
2020-04-28 3:53 ` Anshuman Khandual
2020-04-28 5:24 ` Christophe Leroy
2020-04-28 5:53 ` Anshuman Khandual
2020-04-28 6:12 ` Christophe Leroy
2020-04-28 7:59 ` Qian Cai
2020-04-28 8:41 ` Qian Cai
2020-04-28 9:21 ` Catalin Marinas
2020-04-29 3:28 ` Anshuman Khandual
2020-04-29 12:52 ` [LKP] " Chen, Rong A
2020-04-29 18:15 ` Catalin Marinas
2020-04-29 18:34 ` Christophe Leroy
2020-04-30 2:38 ` Anshuman Khandual
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=51dcbcbf-6020-6672-05b0-5bb10c6292b5@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=borntraeger@de.ibm.com \
--cc=bp@alien8.de \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@c-s.fr \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulus@samba.org \
--cc=rppt@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=vgupta@synopsys.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®