From: Thomas Gleixner <tglx@linutronix.de>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkft-triage@lists.linaro.org,
Andrew Morton <akpm@linux-foundation.org>,
Ira Weiny <ira.weiny@intel.com>,
Oliver Sang <oliver.sang@intel.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
X86 ML <x86@kernel.org>, Kalesh Singh <kaleshsingh@google.com>
Subject: Re: BUG: unable to handle page fault for address - EIP: __kmap_local_page_prot
Date: Thu, 20 May 2021 14:51:48 +0200 [thread overview]
Message-ID: <87tumxbmaj.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CA+G9fYsogFQZSeFyGinZ_EQOEW11cmU5oxuEoDuwyCVNaXv3yA@mail.gmail.com>
On Thu, May 20 2021 at 12:40, Naresh Kamboju wrote:
> On Thu, 20 May 2021 at 00:20, Thomas Gleixner <tglx@linutronix.de> wrote:
>
> The below patch did not solve the reported problem.
> after applying this patch
> CONFIG_HAVE_MOVE_PUD
> disappeared from the config.
> but still i see WARNING: and BUG: when running LTP mm tests.
Yes, but that's a different warning ....
> Test log link,
> FYI,
> i386 kernel Image running on x86_64 machine.
> https://lkft.validation.linaro.org/scheduler/job/2749690#L10139
Sorry, but this webpage is making my browser go apeshit and finding
anything in that gunk of user space messages is a pain. Can we please
have a proper plain dmesg?
Thanks,
tglx
next prev parent reply other threads:[~2021-05-20 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 15:08 BUG: unable to handle page fault for address - EIP: __kmap_local_page_prot Naresh Kamboju
2021-05-19 15:31 ` Matthew Wilcox
2021-05-19 18:50 ` Thomas Gleixner
2021-05-19 19:22 ` Peter Zijlstra
2021-05-20 7:10 ` Naresh Kamboju
2021-05-20 12:51 ` Thomas Gleixner [this message]
2021-05-20 13:04 ` Naresh Kamboju
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=87tumxbmaj.ffs@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=akpm@linux-foundation.org \
--cc=ira.weiny@intel.com \
--cc=kaleshsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=oliver.sang@intel.com \
--cc=x86@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 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.