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@xxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxx
Reporter: newsmails@xxxxxxxxxxxxxxx
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?
