gdrdrv_remap_gpu_mem:error -22, in remap_pfn_range()
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c, linux
- Domain
- operating-systems
Research direction
Start by tracing gdrdrv_mmap and gdrdrv_remap_gpu_mem at the remap_pfn_range() call, using the logged non-contiguous page addresses and -22 return as the reproduction clue. Done should include a confirmed cause for the mapping failure and a documented validation path; the payload names no test or reproduction command.
Written by the indexing model from the issue text.
Description
[14916.488532] gdrdrv:gdrdrv_pin_buffer:invoking nvidia_p2p_get_pages(va=0x7fba65a20000 len=262144 p2p_tok=0 va_tok=0)
[14916.489847] gdrdrv:gdrdrv_pin_buffer:page table entries: 4
[14916.489850] gdrdrv:gdrdrv_pin_buffer:page[0]=0x000003b000c20000
[14916.489852] gdrdrv:gdrdrv_pin_buffer:page[1]=0x000003b000c30000
[14916.489853] gdrdrv:gdrdrv_pin_buffer:page[2]=0x000003b000c40000
[14916.489854] gdrdrv:gdrdrv_pin_buffer:page[3]=0x000003b006050000
[14916.489863] gdrdrv:gdrdrv_mmap:mmap filp=0xffff9025aabe0600 vma=0xffff8fe965ef3290 vm_file=0xffff9025aabe0600 start=0x7fb9a5169000 size=262144 off=0x2240
[14916.489865] gdrdrv:gdrdrv_mmap:range start with p=0 vaddr=7fb9a5169000 page_paddr=3b000c20000
[14916.489866] gdrdrv:gdrdrv_mmap:non-contig p=3 prev_page_paddr=3b000c40000 cur_page_paddr=3b006050000
[14916.489868] gdrdrv:gdrdrv_mmap:mapping p=3 entries=3 offset=0 len=196608 vaddr=7fb9a5169000 paddr=3b000c20000 is_wcomb=1
[14916.489873] gdrdrv:gdrdrv_remap_gpu_mem:error -22, in remap_pfn_range()
[14916.489875] gdrdrv:gdrdrv_mmap:error -22 in gdrdrv_remap_gpu_mem(vaddr=7fb9a5169000, len=196608
[15081.321727] gdrdrv:gdrdrv_pin_buffer:invoking nvidia_p2p_get_pages(va=0x7fba65a20000 len=196608 p2p_tok=0 va_tok=0)
- Dominant language
- C
- Stars
- 1.4k
- Forks
- 198
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/gdrcopy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Proposal: honor `TMPDIR` in gdrcopy package build scriptsPossibly taken @efegokdemir claimed this 53 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Similar issues
-
SPIDevice selects an active-high device as soon as it is createdPossibly taken @mikeysklar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
adafruit/circuitpython#11869 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
gnif/LookingGlass#1352 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
bazel-contrib/rules_go#4784 · 1 comment ·
Maintainers usually reply within 1 day