From: Joerg Roedel <jroedel@suse.de>
To: lkp@lists.01.org
Subject: Re: 0604a4fd53 ("x86/mm: remove vmalloc faulting"): [ 80.661587] BUG: unable to handle page fault for address: fb40c000
Date: Thu, 28 May 2020 11:14:55 +0200 [thread overview]
Message-ID: <20200528091454.GD6857@suse.de> (raw)
In-Reply-To: <20200528084208.GV12456@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
On Thu, May 28, 2020 at 04:42:09PM +0800, kernel test robot wrote:
> [ 80.686904] Code: 89 c8 c3 90 8d 74 26 00 85 c0 c7 01 01 00 00 00 75 d8 a1 6c 94 a8 08 eb d1 66 90 66 90 66 90 66 90 66 90 66 90 66 90 90 cd 80 <c3> 8d b6 00 00 00 00 8d bc 27 00 00 00 00 8b 10 a3 94 94 a8 08 85
> [ 80.690396] EAX: ffffffda EBX: 00000132 ECX: a6f11000 EDX: 00000000
> [ 80.691639] ESI: 00000024 EDI: 0000fffc EBP: 0000fff8 ESP: afef5ae8
> [ 80.692918] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000292
> [ 80.694316] Modules linked in:
> [ 80.694962] CR2: 00000000fb40c000
> [ 80.695729] ---[ end trace eda436684f987d33 ]---
> [ 80.696742] EIP: __vmalloc_node_range+0x16d/0x470
Looking into it.
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <jroedel@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
LKP <lkp@lists.01.org>
Subject: Re: 0604a4fd53 ("x86/mm: remove vmalloc faulting"): [ 80.661587] BUG: unable to handle page fault for address: fb40c000
Date: Thu, 28 May 2020 11:14:55 +0200 [thread overview]
Message-ID: <20200528091454.GD6857@suse.de> (raw)
In-Reply-To: <20200528084208.GV12456@shao2-debian>
On Thu, May 28, 2020 at 04:42:09PM +0800, kernel test robot wrote:
> [ 80.686904] Code: 89 c8 c3 90 8d 74 26 00 85 c0 c7 01 01 00 00 00 75 d8 a1 6c 94 a8 08 eb d1 66 90 66 90 66 90 66 90 66 90 66 90 66 90 90 cd 80 <c3> 8d b6 00 00 00 00 8d bc 27 00 00 00 00 8b 10 a3 94 94 a8 08 85
> [ 80.690396] EAX: ffffffda EBX: 00000132 ECX: a6f11000 EDX: 00000000
> [ 80.691639] ESI: 00000024 EDI: 0000fffc EBP: 0000fff8 ESP: afef5ae8
> [ 80.692918] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000292
> [ 80.694316] Modules linked in:
> [ 80.694962] CR2: 00000000fb40c000
> [ 80.695729] ---[ end trace eda436684f987d33 ]---
> [ 80.696742] EIP: __vmalloc_node_range+0x16d/0x470
Looking into it.
next prev parent reply other threads:[~2020-05-28 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 8:42 0604a4fd53 ("x86/mm: remove vmalloc faulting"): [ 80.661587] BUG: unable to handle page fault for address: fb40c000 kernel test robot
2020-05-28 8:42 ` kernel test robot
2020-05-28 9:14 ` Joerg Roedel [this message]
2020-05-28 9:14 ` Joerg Roedel
2020-05-28 18:48 ` Joerg Roedel
2020-05-28 18:48 ` Joerg Roedel
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=20200528091454.GD6857@suse.de \
--to=jroedel@suse.de \
--cc=lkp@lists.01.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.