You are not logged in.

#1 2023-06-15 19:34:33

Dotslash
Member
Registered: 2012-02-02
Posts: 62

Solved - journalctl errors - cannot map memory and nvidia error

Hello, so I sometimes open journalctl and I've been seeing alot of this error and was wondering what it is and if i should be concerned. It seems to happen when I run steam.

Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fca000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fc8000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fc6000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fc4000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fc2000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fc0000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fbe000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fbc000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fba000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fb8000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fb6000 and size of 0x2 pages
Jun 15 11:46:47 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fb4000 and size of 0x2 pages
Jun 15 11:46:48 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fb1000 and size of 0x2 pages
Jun 15 11:46:48 archlinux kernel: Cannot map memory with base addr 0x7f9ee9faf000 and size of 0x2 pages
Jun 15 11:46:48 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fad000 and size of 0x2 pages
Jun 15 11:46:48 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fab000 and size of 0x2 pages
Jun 15 11:46:48 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fa9000 and size of 0x2 pages
Jun 15 11:46:48 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fa7000 and size of 0x2 pages
Jun 15 11:46:48 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fa5000 and size of 0x2 pages
Jun 15 11:46:48 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fa3000 and size of 0x2 pages
Jun 15 11:46:49 archlinux kernel: Cannot map memory with base addr 0x7f9ee9fa1000 and size of 0x2 pages
Jun 15 11:46:49 archlinux kernel: Cannot map memory with base addr 0x7f9ee9f9f000 and size of 0x2 pages
Jun 15 11:46:49 archlinux kernel: Cannot map memory with base addr 0x7f9ee9f9d000 and size of 0x2 pages
Jun 15 11:46:49 archlinux kernel: Cannot map memory with base addr 0x7f9ee9f9b000 and size of 0x2 pages
Jun 15 11:46:49 archlinux kernel: Cannot map memory with base addr 0x7f9ee9e51000 and size of 0x14a pages
Jun 15 11:46:49 archlinux kernel: Cannot map memory with base addr 0x7f9ee9d07000 and size of 0x14a pages
Jun 15 11:46:49 archlinux kernel: Cannot map memory with base addr 0x7f9ee9bbd000 and size of 0x14a pages
Jun 15 11:46:49 archlinux kernel: Cannot map memory with base addr 0x7f9ee9a73000 and size of 0x14a pages
Jun 15 11:46:49 archlinux kernel: Cannot map memory with base addr 0x7f9ee9929000 and size of 0x14a pages
Jun 15 11:46:49 archlinux kernel: Cannot map memory with base addr 0x7f9ee97df000 and size of 0x14a pages
Jun 15 11:47:00 archlinux kernel: Cannot map memory with base addr 0x7f9ee5a89000 and size of 0x3e8 pages

I'm also seeing this too. I have a nvidia gtx 970. I'm kinda wondering if these are signs of the video card dying? I have been playing some games without any crashing.

Jun 15 11:42:27 archlinux kernel: ------------[ cut here ]------------
Jun 15 11:42:27 archlinux kernel: Unhandled error in __nv_drm_gem_user_memory_handle_vma_fault: -22
Jun 15 11:42:27 archlinux kernel: WARNING: CPU: 3 PID: 598 at /build/nvidia/src/nvidia/535.54.03/build/nvidia-drm/nvidia-drm-gem-user-memory.c:130 __nv_drm_gem_user_memory_handle_vma_fault+0x8f/0xa0 [nvidia_drm]
Jun 15 11:42:27 archlinux kernel: Modules linked in: ccm algif_aead cbc des_generic libdes ecb algif_skcipher cmac md4 algif_hash af_alg nct6775 nct6775_core hwmon_vid ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrt>
Jun 15 11:42:27 archlinux kernel:  snd_hwdep cryptd sparse_keymap cfg80211 mei_hdcp platform_profile iTCO_wdt snd_pcm mei_pxp rapl intel_pmc_bxt intel_cstate iTCO_vendor_support snd_timer ee1004 mei_me snd wmi_bmof mxm_wmi video i2c_i801 e1000e intel_uncore rfkill soundcor>
Jun 15 11:42:27 archlinux kernel: CPU: 3 PID: 598 Comm: Xorg Tainted: P           OE      6.3.8-arch1-1 #1 a1d299e746aebdb27c523dd3bd94aba6f54915c7
Jun 15 11:42:27 archlinux kernel: Hardware name: System manufacturer System Product Name/ROG STRIX Z370-H GAMING, BIOS 2402 06/17/2020
Jun 15 11:42:27 archlinux kernel: RIP: 0010:__nv_drm_gem_user_memory_handle_vma_fault+0x8f/0xa0 [nvidia_drm]
Jun 15 11:42:27 archlinux kernel: Code: ba 00 01 00 00 89 d0 c3 cc cc cc cc 0f 0b 89 c2 48 c7 c6 60 39 95 c0 48 c7 c7 c3 3c 95 c0 c6 05 9e a0 00 00 01 e8 91 01 16 e5 <0f> 0b eb c6 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90 90 90 90
Jun 15 11:42:27 archlinux kernel: RSP: 0018:ffffad89841e39e0 EFLAGS: 00010286
Jun 15 11:42:27 archlinux kernel: RAX: 0000000000000000 RBX: ffffad89841e3a50 RCX: 0000000000000027
Jun 15 11:42:27 archlinux kernel: RDX: ffffa0561eae1688 RSI: 0000000000000001 RDI: ffffa0561eae1680
Jun 15 11:42:27 archlinux kernel: RBP: ffffa0539924e320 R08: 0000000000000000 R09: ffffad89841e3870
Jun 15 11:42:27 archlinux kernel: R10: 0000000000000003 R11: ffffffffa78ca1e8 R12: ffffa0539924e320
Jun 15 11:42:27 archlinux kernel: R13: 0000000000000440 R14: 0000000122553067 R15: ffffa052d3e96410
Jun 15 11:42:27 archlinux kernel: FS:  00007fa092d64480(0000) GS:ffffa0561eac0000(0000) knlGS:0000000000000000
Jun 15 11:42:27 archlinux kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 15 11:42:27 archlinux kernel: CR2: 00007f65ab85cc2c CR3: 0000000113d48006 CR4: 00000000003706e0
Jun 15 11:42:27 archlinux kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jun 15 11:42:27 archlinux kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jun 15 11:42:27 archlinux kernel: Call Trace:
Jun 15 11:42:27 archlinux kernel:  <TASK>
Jun 15 11:42:27 archlinux kernel:  ? __nv_drm_gem_user_memory_handle_vma_fault+0x8f/0xa0 [nvidia_drm d83046505765400366d251e55b036a6fb3a8e93d]
Jun 15 11:42:27 archlinux kernel:  ? __warn+0x81/0x130
Jun 15 11:42:27 archlinux kernel:  ? __nv_drm_gem_user_memory_handle_vma_fault+0x8f/0xa0 [nvidia_drm d83046505765400366d251e55b036a6fb3a8e93d]
Jun 15 11:42:27 archlinux kernel:  ? report_bug+0x171/0x1a0
Jun 15 11:42:27 archlinux kernel:  ? prb_read_valid+0x1b/0x30
Jun 15 11:42:27 archlinux kernel:  ? handle_bug+0x3c/0x80
Jun 15 11:42:27 archlinux kernel:  ? exc_invalid_op+0x17/0x70
Jun 15 11:42:27 archlinux kernel:  ? asm_exc_invalid_op+0x1a/0x20
Jun 15 11:42:27 archlinux kernel:  ? __nv_drm_gem_user_memory_handle_vma_fault+0x8f/0xa0 [nvidia_drm d83046505765400366d251e55b036a6fb3a8e93d]
Jun 15 11:42:27 archlinux kernel:  __do_fault+0x30/0x130
Jun 15 11:42:27 archlinux kernel:  do_fault+0x299/0x410
Jun 15 11:42:27 archlinux kernel:  __handle_mm_fault+0x685/0xfe0
Jun 15 11:42:27 archlinux kernel:  handle_mm_fault+0x11e/0x310
Jun 15 11:42:27 archlinux kernel:  __get_user_pages+0x1f5/0x650
Jun 15 11:42:27 archlinux kernel:  __gup_longterm_locked+0xea/0xca0
Jun 15 11:42:27 archlinux kernel:  ? __kmem_cache_alloc_node+0x18d/0x310
Jun 15 11:42:27 archlinux kernel:  ? os_alloc_mem+0xc8/0xe0 [nvidia 1ed7baa98ad62b9936313996cbb104df03c4010d]
Jun 15 11:42:27 archlinux kernel:  ? os_alloc_mem+0xc8/0xe0 [nvidia 1ed7baa98ad62b9936313996cbb104df03c4010d]
Jun 15 11:42:27 archlinux kernel:  pin_user_pages+0x78/0xb0
Jun 15 11:42:27 archlinux kernel:  os_lock_user_pages+0xc6/0x1b0 [nvidia 1ed7baa98ad62b9936313996cbb104df03c4010d]
Jun 15 11:42:27 archlinux kernel:  _nv000648rm+0x67/0x160 [nvidia 1ed7baa98ad62b9936313996cbb104df03c4010d]
Jun 15 11:42:27 archlinux kernel:  _nv000714rm+0xa71/0xe70 [nvidia 1ed7baa98ad62b9936313996cbb104df03c4010d]
Jun 15 11:42:27 archlinux kernel:  rm_ioctl+0x58/0xb0 [nvidia 1ed7baa98ad62b9936313996cbb104df03c4010d]
Jun 15 11:42:27 archlinux kernel:  nvidia_ioctl+0x5d8/0x880 [nvidia 1ed7baa98ad62b9936313996cbb104df03c4010d]
Jun 15 11:42:27 archlinux kernel:  nvidia_frontend_unlocked_ioctl+0x39/0x50 [nvidia 1ed7baa98ad62b9936313996cbb104df03c4010d]
Jun 15 11:42:27 archlinux kernel:  __x64_sys_ioctl+0x91/0xd0
Jun 15 11:42:27 archlinux kernel:  do_syscall_64+0x5d/0x90
Jun 15 11:42:27 archlinux kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
Jun 15 11:42:27 archlinux kernel:  ? do_syscall_64+0x6c/0x90
Jun 15 11:42:27 archlinux kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jun 15 11:42:27 archlinux kernel: RIP: 0033:0x7fa09374076f
Jun 15 11:42:27 archlinux kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
Jun 15 11:42:27 archlinux kernel: RSP: 002b:00007ffde5d70310 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jun 15 11:42:27 archlinux kernel: RAX: ffffffffffffffda RBX: 00000000000000b8 RCX: 00007fa09374076f
Jun 15 11:42:27 archlinux kernel: RDX: 00007ffde5d70510 RSI: 00000000c0b8464a RDI: 000000000000000f
Jun 15 11:42:27 archlinux kernel: RBP: 00007ffde5d70510 R08: 00007ffde5d70510 R09: 00007ffde5d70524
Jun 15 11:42:27 archlinux kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 000000000000000f
Jun 15 11:42:27 archlinux kernel: R13: 00007ffde5d70370 R14: 00000000c0b8464a R15: 000000000000004a
Jun 15 11:42:27 archlinux kernel:  </TASK>
Jun 15 11:42:27 archlinux kernel: ---[ end trace 0000000000000000 ]---

Last edited by Dotslash (2023-06-17 18:01:21)

Offline

#2 2023-06-15 20:21:58

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,659

Re: Solved - journalctl errors - cannot map memory and nvidia error

https://www.mail-archive.com/ubuntu-bug … 23597.html

zgrep -i huge /proc/config.gz

(yes, is likely enabled - you don't have to post that)

You don't seem to have any other GPU, though?
Either way, out of context this doesn't mean much wrt you HW condition.

Offline

#3 2023-06-15 20:58:19

Dotslash
Member
Registered: 2012-02-02
Posts: 62

Re: Solved - journalctl errors - cannot map memory and nvidia error

Yeah only one video card, ok thanks.

Offline

#4 2023-06-16 06:18:20

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,659

Re: Solved - journalctl errors - cannot map memory and nvidia error

If you want a more informed comment, you'll have to post the system journal.
Otherwise, if there's no question left, please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

Board footer

Powered by FluxBB