[Bug 237435] [aarch64][KASSERT] panic: pmap_demote_l2: Invalid virtual address - in sys_mprotect while building lang/sbcl with lang/clisp

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237435

            Bug ID: 237435
           Summary: [aarch64][KASSERT] panic: pmap_demote_l2: Invalid
                    virtual address - in sys_mprotect while building
                    lang/sbcl with lang/clisp
           Product: Base System
           Version: CURRENT
          Hardware: arm64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: arm
          Assignee: freebsd-arm at FreeBSD.org
          Reporter: greg at unrelenting.technology

Added clisp as an option for building sbcl on non-x86 platforms (clisp itself
requires removing BROKEN in a dependency - bug 237432). When building, an
mprotect call fails an assertion:

panic: pmap_demote_l2: Invalid virtual address 0x2e0004a7b000
cpuid = 20
time = 1555847196
KDB: stack backtrace:
db_trace_self() at db_trace_self_wrapper+0x28
         pc = 0xffff0000006fcb70  lr = 0xffff000000123b94
         sp = 0xffff000103ea44c0  fp = 0xffff000103ea46d0

db_trace_self_wrapper() at vpanic+0x18c
         pc = 0xffff000000123b94  lr = 0xffff0000003e8e2c
         sp = 0xffff000103ea46e0  fp = 0xffff000103ea4790

vpanic() at panic+0x44
         pc = 0xffff0000003e8e2c  lr = 0xffff0000003e8bf4
         sp = 0xffff000103ea47a0  fp = 0xffff000103ea4820

panic() at pmap_demote_l2_locked+0xadc
         pc = 0xffff0000003e8bf4  lr = 0xffff00000070e674
         sp = 0xffff000103ea4830  fp = 0xffff000103ea48d0

pmap_demote_l2_locked() at pmap_protect+0x1dc
         pc = 0xffff00000070e674  lr = 0xffff00000070f4d0
         sp = 0xffff000103ea48e0  fp = 0xffff000103ea4940

pmap_protect() at vm_map_protect+0x2ec
         pc = 0xffff00000070f4d0  lr = 0xffff0000006ae188
         sp = 0xffff000103ea4950  fp = 0xffff000103ea49b0

vm_map_protect() at sys_mprotect+0x58
         pc = 0xffff000  sp = 0xffff000103ea49c0  fp = 0xffff000103ea49c0

sys_mprotect() at do_el0_sync+0x4fc
         pc = 0xffff0000006b3758  lr = 0xffff000000717c58
         sp = 0xffff000103ea49d0  fp = 0xffff000103ea4a70

do_el0_sync() at handle_el0_sync+0x84
         pc = 0xffff000000717c58  lr = 0xffff0000006fea00
         sp = 0xffff000103ea4a80  fp = 0xffff000103ea4b90

handle_el0_sync() at 0x43a83c
         pc = 0xffff0000006fea00  lr = 0x000000000043a83c
         sp = 0xffff000103ea4ba0  fp = 0x0000fffffffee930

The panic does not happen on a NODEBUG kernel and nothing bad seems to happen
after that :)

-- 
You are receiving this mail because:
You are the assignee for the bug.