[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+G9fYvUPmr0_WFRGprOw_N1Jik9TZ5JzgbdbdR_yZLMezZZCQ@mail.gmail.com>
Date: Mon, 16 May 2022 21:57:19 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Liam Howlett <liam.howlett@...cle.com>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"lkft-triage@...ts.linaro.org" <lkft-triage@...ts.linaro.org>,
Yang Shi <shy828301@...il.com>,
Vlastimil Babka <vbabka@...e.cz>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Miaohe Lin <linmiaohe@...wei.com>,
Song Liu <songliubraving@...com>,
Rik van Riel <riel@...riel.com>,
Matthew Wilcox <willy@...radead.org>, Zi Yan <ziy@...dia.com>,
"Theodore Ts'o" <tytso@....edu>, Song Liu <song@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
David Howells <dhowells@...hat.com>,
SeongJae Park <sj@...nel.org>, Will Deacon <will@...nel.org>,
Davidlohr Bueso <dave@...olabs.net>
Subject: Re: [next ] kernel BUG at mm/mmap.c:3235! - invalid opcode: 0000 [#1]
PREEMPT SMP NOPTI
Hi Liam,
On Mon, 16 May 2022 at 21:06, Liam Howlett <liam.howlett@...cle.com> wrote:
>
> * Naresh Kamboju <naresh.kamboju@...aro.org> [220516 02:51]:
> > While running LTP mm tests on x86_64 the following kernel BUG was noticed
> > on Linux next-20220513 [1].
> >
> > mmapstress01 1 TPASS : Test passed
> > mmapstress02 1 TPASS : Test passed
> > mmapstress03 0 TINFO : uname.machine=x86_64 kernel is 64bit
> > mmapstress03 1 TPASS : Test passed
> > [ 666.897222] ------------[ cut here ]------------
> > [ 666.897260] kernel BUG at mm/mmap.c:3235!
> > [ 666.897285] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
> > [ 666.899420] CPU: 3 PID: 25230 Comm: mmapstress03 Not tainted
> > 5.18.0-rc6-next-20220513 #1
> > [ 666.900552] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
> > BIOS 1.12.0-1 04/01/2014
> > [ 666.901868] RIP: 0010:exit_mmap+0x32c/0x3a0
<trim>
> > Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> >
> >
> > metadata:
> > git_ref: master
> > git_repo: ''
> > git_sha: 1e1b28b936aed946122b4e0991e7144fdbbfd77e
> > git_describe: next-20220513
> > kernel_version: 5.18.0-rc6
Here is the Kconfig file.
> > kernel-config: https://builds.tuxbuild.com/296PqKcUcCQSykZbASUqmdlP33g/config
> > build-url: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/pipelines/538244935
> > artifact-location: https://builds.tuxbuild.com/296PqKcUcCQSykZbASUqmdlP33g
> > toolchain: clang-12
>
> I'm having an issue reproducing this on my configuration. May be the
> clang compiler though. I'll keep digging.
FYI,
tuxmake will set up toolchains for you and build fast.
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
#
# See https://docs.tuxmake.org/ for complete documentation.
# Original tuxmake command with fragments listed below.
# tuxmake --runtime podman --target-arch x86_64 --toolchain clang-12
--kconfig defconfig --kconfig-add
https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft.config
--kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft-crypto.config
--kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/distro-overrides.config
--kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/systemd.config
--kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/virtio.config
--kconfig-add CONFIG_IGB=y --kconfig-add
CONFIG_UNWINDER_FRAME_POINTER=y LLVM=1 LLVM_IAS=1
( OR )
tuxmake --runtime podman --target-arch x86_64 --toolchain clang-12
--kconfig https://builds.tuxbuild.com/296PqKcUcCQSykZbASUqmdlP33g/config
LLVM=1 LLVM_IAS=1
- Naresh
Powered by blists - more mailing lists