From: Mel Gorman <mgorman@techsingularity.net>
To: Oleksandr Natalenko <oleksandr@redhat.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 5.1 and 5.1.1: BUG: unable to handle kernel paging request at ffffea0002030000
Date: Mon, 27 May 2019 09:25:13 +0100 [thread overview]
Message-ID: <20190527082513.GR18914@techsingularity.net> (raw)
In-Reply-To: <20190527062301.rk32mhnk2qy2ives@butterfly.localdomain>
On Mon, May 27, 2019 at 08:23:01AM +0200, Oleksandr Natalenko wrote:
> On Fri, May 24, 2019 at 01:31:46PM +0100, Mel Gorman wrote:
> > On Fri, May 24, 2019 at 01:43:29PM +0200, Oleksandr Natalenko wrote:
> > > > Please use the offset 0xb9
> > > >
> > > > addr2line -i -e /usr/src/linux/vmlinux `printf "0x%lX" $((0x$ADDR+0xb9))
> > > >
> > > > --
> > > > Mel Gorman
> > > > SUSE Labs
> > >
> > > Cc'ing myself since i observe such a behaviour sometimes right after KVM
> > > VM is launched. No luck with reproducing it on demand so far, though.
> > >
> >
> > It's worth testing the patch at https://lore.kernel.org/lkml/1558689619-16891-1-git-send-email-suzuki.poulose@arm.com/T/#u
>
> It is reported [1] that this fixes the issue.
>
> Thanks.
>
> [1] https://github.com/NixOS/nixpkgs/issues/61909
>
Thanks! The patch has been picked up by Andrew and it's marked for
-stable. It should make its way into a stable release eventually.
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2019-05-27 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 8:27 5.1 and 5.1.1: BUG: unable to handle kernel paging request at ffffea0002030000 Justin Piszcz
2019-05-12 8:34 ` Justin Piszcz
2019-05-17 21:30 ` Sakari Ailus
2019-05-20 11:56 ` Mel Gorman
2019-05-20 12:20 ` Justin Piszcz
2019-05-21 9:01 ` Justin Piszcz
2019-05-21 12:43 ` Mel Gorman
2019-05-24 11:43 ` Oleksandr Natalenko
2019-05-24 12:31 ` Mel Gorman
2019-05-24 12:38 ` Oleksandr Natalenko
2019-05-27 6:23 ` Oleksandr Natalenko
2019-05-27 8:25 ` Mel Gorman [this message]
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=20190527082513.GR18914@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@redhat.com \
/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.