Regression on NFS: unable to handle page fault in mempool_alloc_slab
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot:
Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: ffff9083e222e632
Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode
Jul 04 16:58:32 hostname kernel: #PF: error_code(0x0000) - not-present page
Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0
Jul 04 16:58:32 hostname kernel: Oops: 0000 [#1] SMP NOPTI
Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu
Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/
Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc]
Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_
Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb
Jul 04 16:58:32 hostname kernel: RSP: 0018:ffffbc38c0
Jul 04 16:58:32 hostname kernel: RAX: ffff9083e222e632 RBX: 0000000000000000 RCX: 0000000000000002
Jul 04 16:58:32 hostname kernel: RDX: 0000000000000009 RSI: 0000000000092800 RDI: 0000000000031fb0
Jul 04 16:58:32 hostname kernel: RBP: ffffbc38c046fcf8 R08: ffff90836c331fb0 R09: ffffffffc1436a94
Jul 04 16:58:32 hostname kernel: R10: ffff908368178d2c R11: 0000000000000018 R12: ffff9083e222e632
Jul 04 16:58:32 hostname kernel: R13: 0000000000092800 R14: ffff908367ca6140 R15: ffff908367ca6140
Jul 04 16:58:32 hostname kernel: FS: 000000000000000
Jul 04 16:58:32 hostname kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 04 16:58:32 hostname kernel: CR2: ffff9083e222e632 CR3: 00000003ab80a003 CR4: 00000000003606e0
Jul 04 16:58:32 hostname kernel: Call Trace:
Jul 04 16:58:32 hostname kernel: ? mempool_
Jul 04 16:58:32 hostname kernel: mempool_
Jul 04 16:58:32 hostname kernel: mempool_
Jul 04 16:58:32 hostname kernel: rpc_malloc+
Jul 04 16:58:32 hostname kernel: call_allocate+
Jul 04 16:58:32 hostname kernel: ? call_refreshres
Jul 04 16:58:32 hostname kernel: __rpc_execute+
Jul 04 16:58:32 hostname kernel: rpc_async_
Jul 04 16:58:32 hostname kernel: process_
Jul 04 16:58:32 hostname kernel: worker_
Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140
Jul 04 16:58:32 hostname kernel: ? process_
Jul 04 16:58:32 hostname kernel: ? kthread_
Jul 04 16:58:32 hostname kernel: ret_from_
Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s>
Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_
Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel
Jul 04 16:58:32 hostname kernel: CR2: ffff9083e222e632
Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]---
Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_
Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb
Jul 04 16:58:32 hostname kernel: RSP: 0018:ffffbc38c0
Jul 04 16:58:32 hostname kernel: RAX: ffff9083e222e632 RBX: 0000000000000000 RCX: 0000000000000002
Jul 04 16:58:32 hostname kernel: RDX: 0000000000000009 RSI: 0000000000092800 RDI: 0000000000031fb0
Jul 04 16:58:32 hostname kernel: RBP: ffffbc38c046fcf8 R08: ffff90836c331fb0 R09: ffffffffc1436a94
Jul 04 16:58:32 hostname kernel: R10: ffff908368178d2c R11: 0000000000000018 R12: ffff9083e222e632
Jul 04 16:58:32 hostname kernel: R13: 0000000000092800 R14: ffff908367ca6140 R15: ffff908367ca6140
Jul 04 16:58:32 hostname kernel: FS: 000000000000000
Jul 04 16:58:32 hostname kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 04 16:58:32 hostname kernel: CR2: ffff9083e222e632 CR3: 00000003ab80a003 CR4: 00000000003606e0
When booting 5.4.0-39-generic the problem does not occur.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CasperMD5CheckR
DistroRelease: Ubuntu 20.04
HibernationDevice: RESUME=
MachineType: LENOVO 20N2CTO1WW
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.187.1
Tags: focal
Uname: Linux 5.4.0-40-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/22/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2IET88W (1.66 )
dmi.board.
dmi.board.name: 20N2CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad T490
dmi.product.name: 20N2CTO1WW
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
CVE References
tags: | added: focal |
description: | updated |
summary: |
- unable to handle page fault in mempool_alloc_slab + Regression on NFS: unable to handle page fault in mempool_alloc_slab |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1886277
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.