From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: 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, 20 May 2019 08:20:03 -0400 [thread overview]
Message-ID: <CAO9zADxf7VdzHWC2C-uCbeqhvN2oTW4KhU=o4GEXfLoVGpEt5w@mail.gmail.com> (raw)
In-Reply-To: <20190520115608.GK18914@techsingularity.net>
On Mon, May 20, 2019 at 7:56 AM Mel Gorman <mgorman@techsingularity.net> wrote:
>
> On Sun, May 12, 2019 at 04:27:45AM -0400, Justin Piszcz wrote:
> > Hello,
> >
> > I've turned off zram/zswap and I am still seeing the following during
> > periods of heavy I/O, I am returning to 5.0.xx in the meantime.
> >
> > Kernel: 5.1.1
> > Arch: x86_64
> > Dist: Debian x86_64
> >
> > [29967.019411] BUG: unable to handle kernel paging request at ffffea0002030000
> > [29967.019414] #PF error: [normal kernel read fault]
> > [29967.019415] PGD 103ffee067 P4D 103ffee067 PUD 103ffed067 PMD 0
> > [29967.019417] Oops: 0000 [#1] SMP PTI
> > [29967.019419] CPU: 10 PID: 77 Comm: khugepaged Tainted: G
> > T 5.1.1 #4
> > [29967.019420] Hardware name: Supermicro X9SRL-F/X9SRL-F, BIOS 3.2 01/16/2015
> > [29967.019424] RIP: 0010:isolate_freepages_block+0xb9/0x310
> > [29967.019425] Code: 24 28 48 c1 e0 06 40 f6 c5 1f 48 89 44 24 20 49
> > 8d 45 79 48 89 44 24 18 44 89 f0 4d 89 ee 45 89 fd 41 89 c7 0f 84 ef
> > 00 00 00 <48> 8b 03 41 83 c4 01 a9 00 00 01 00 75 0c 48 8b 43 08 a8 01
> > 0f 84
>
> If you have debugging symbols installed, can you translate the faulting
> address with the following?
>
> ADDR=`nm /path/to/vmlinux-or-debuginfo-file | grep "t isolate_freepages_block\$" | awk '{print $1}'`
> addr2line -i -e vmlinux `printf "0x%lX" $((0x$ADDR+0xb9))`
>
> I haven't seen this particular error before so I want to see if the
> faulting address could have anything to do with the randomising of
> struct fields. Similarly a full dmesg log would be nice so I can see
> what your memory layout looks like.
>
> Thanks Justin.
Hello,
DMESG output in the interim:
http://installkernel.tripod.com/20190520_dmesg_full.txt
Once the error happens again I will post another dmesg link and get
the addr2line output.
Justin.
next prev parent reply other threads:[~2019-05-20 12:50 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 [this message]
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
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='CAO9zADxf7VdzHWC2C-uCbeqhvN2oTW4KhU=o4GEXfLoVGpEt5w@mail.gmail.com' \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
/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.