Just saw this on 5.3.0-62-generic on 18.04. When this happens, kernel gets a stack trace on BUG. The problem is not in nfs-utils, but a new bug in kernel, likely exactly kernel version 5.3.0-62-generic, since this popped up right after kernel update.
Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681409] BUG: unable to handle page fault for address: ffff90f1ce3b673e Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681414] #PF: supervisor read access in kernel mode Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681414] #PF: error_code(0x0000) - not-present page Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681415] PGD b3402067 P4D b3402067 PUD 0 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681418] Oops: 0000 [#1] SMP PTI Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681420] CPU: 0 PID: 3777 Comm: kworker/u4:2 Not tainted 5.3.0-62-generic #56~18.04.1-Ubuntu Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681421] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/ 2018 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681441] Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681474] RIP: 0010:kmem_cache_alloc+0x7e/0x220 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681476] Code: ba 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 80 29 57 5e 4d 8b 20 4d 85 e4 0f 84 66 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 49 33 9f 70 01 00 00 48 89 c1 48 0f c9 4c 89 e0 48 31 cb Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681477] RSP: 0018:ffffb4a7036dbcd8 EFLAGS: 00010282 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681478] RAX: ffff90f1ce3b673e RBX: 0000000000092800 RCX: 0000000000000002 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681479] RDX: 000000000000002c RSI: 0000000000092800 RDI: 0000000000031d70 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681480] RBP: ffffb4a7036dbd08 R08: ffff90f17aa31d70 R09: 8080808080808080 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681480] R10: ffffffffa2e03d10 R11: fefefefefefefeff R12: ffff90f1ce3b673e Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681481] R13: 0000000000092800 R14: ffff90f17999e000 R15: ffff90f17999e000 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681482] FS: 0000000000000000(0000) GS:ffff90f17aa00000(0000) knlGS:0000000000000000 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681483] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681484] CR2: ffff90f1ce3b673e CR3: 0000000136de0004 CR4: 00000000003606f0 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681512] Call Trace: Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681522] ? mempool_alloc_slab+0x15/0x20 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681537] ? wait_woken+0x80/0x80 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681539] mempool_alloc_slab+0x15/0x20 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681540] mempool_alloc+0x71/0x190 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681548] rpc_malloc+0x9d/0xd0 [sunrpc] Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681555] call_allocate+0xbb/0x1f0 [sunrpc] Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681560] ? call_refreshresult+0x140/0x140 [sunrpc] Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681567] ? rpc_exit+0x30/0x30 [sunrpc] Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681574] __rpc_execute+0x8a/0x420 [sunrpc] Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681590] ? __switch_to_asm+0x34/0x70 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681597] rpc_async_schedule+0x30/0x50 [sunrpc] Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681607] process_one_work+0x1fd/0x3f0 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681609] worker_thread+0x34/0x410 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681610] kthread+0x121/0x140 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681611] ? process_one_work+0x3f0/0x3f0 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681612] ? kthread_park+0xb0/0xb0 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681614] ret_from_fork+0x35/0x40 Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681615] Modules linked in: cmac nls_utf8 cifs libarc4 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter bpfilter intel_rapl_msr intel_rapl_common sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd vmw_balloon cryptd glue_helper intel_rapl_perf input_leds joydev serio_raw vmw_vsock_vmci_transport vsock vmw_vmci mac_hid binfmt_misc sch_fq_codel cuse parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_generic usbhid hid psmouse vmwgfx ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops vmxnet3 drm ahci libahci vmw_pvscsi i2c_piix4 pata_acpi Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681673] CR2: ffff90f1ce3b673e Jul 13 13:04:10 vdi-cubic-022 kernel: [ 3140.681674] ---[ end trace 3250bf5f71380240 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887241 Title: connection to a nfs volume from a client freezes the whole server randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1887241/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
