From: Vlastimil Babka <vbabka@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>, newsmails@netcourrier.com
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
Song Liu <songliubraving@fb.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [Bug 210031] New: unable to handle page fault for address - EIP: khugepaged
Date: Wed, 4 Nov 2020 13:14:12 +0100 [thread overview]
Message-ID: <86e33bed-eb81-3966-b195-431742f86746@suse.cz> (raw)
In-Reply-To: <20201103161753.27a58af99ba35b94660e8fa3@linux-foundation.org>
On 11/4/20 1:17 AM, Andrew Morton wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
>
> On Tue, 03 Nov 2020 20:00:58 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=210031
>>
>> Bug ID: 210031
>> Summary: unable to handle page fault for address - EIP:
>> khugepaged
>> Product: Memory Management
>> Version: 2.5
>> Kernel Version: 5.9.1
>> Hardware: All
>> OS: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: normal
>> Priority: P1
>> Component: Other
>> Assignee: akpm@linux-foundation.org
>> Reporter: newsmails@netcourrier.com
>> Regression: No
>
> Thanks. That's a strange looking trace. I'll optimistically cc some
> people who have been working in that area lately.
>
> What caused this kernel to be tainted?
>
>
>> laptop Skylake i915
>> Distribution : slackware 14.2 32 bits
>>
>> Oct 23 17:38:22 linuxp kernel: [141330.499234] BUG: unable to handle page fault
>> for address: 021d202d
>> Oct 23 17:38:22 linuxp kernel: [141330.499245] #PF: supervisor read access in
>> kernel mode
>> Oct 23 17:38:22 linuxp kernel: [141330.499250] #PF: error_code(0x0000) -
>> not-present page
>> Oct 23 17:38:22 linuxp kernel: [141330.499265] Oops: 0000 [#2] SMP PTI
#2 means this is not the first oops. Do you have the very first?
next prev parent reply other threads:[~2020-11-04 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-210031-27@https.bugzilla.kernel.org/>
2020-11-04 0:17 ` Andrew Morton
2020-11-04 9:03 ` Newsmails
2020-11-04 12:14 ` Vlastimil Babka [this message]
2020-11-04 12:23 ` Newsmails
2020-11-04 12:45 ` Vlastimil Babka
2020-11-09 11:47 ` Newsmails
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=86e33bed-eb81-3966-b195-431742f86746@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=newsmails@netcourrier.com \
--cc=oleg@redhat.com \
--cc=songliubraving@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox