Date: Sun, 21 Apr 2019 12:19:11 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 237435] [aarch64][KASSERT] panic: pmap_demote_l2: Invalid virtual address - in sys_mprotect while building lang/sbcl with lang/clisp Message-ID: <bug-237435-7@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237435 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@FreeBSD.org Reporter: greg@unrelenting.technology Added clisp as an option for building sbcl on non-x86 platforms (clisp itse= lf 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 =3D 20 time =3D 1555847196 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc =3D 0xffff0000006fcb70 lr =3D 0xffff000000123b94 sp =3D 0xffff000103ea44c0 fp =3D 0xffff000103ea46d0 db_trace_self_wrapper() at vpanic+0x18c pc =3D 0xffff000000123b94 lr =3D 0xffff0000003e8e2c sp =3D 0xffff000103ea46e0 fp =3D 0xffff000103ea4790 vpanic() at panic+0x44 pc =3D 0xffff0000003e8e2c lr =3D 0xffff0000003e8bf4 sp =3D 0xffff000103ea47a0 fp =3D 0xffff000103ea4820 panic() at pmap_demote_l2_locked+0xadc pc =3D 0xffff0000003e8bf4 lr =3D 0xffff00000070e674 sp =3D 0xffff000103ea4830 fp =3D 0xffff000103ea48d0 pmap_demote_l2_locked() at pmap_protect+0x1dc pc =3D 0xffff00000070e674 lr =3D 0xffff00000070f4d0 sp =3D 0xffff000103ea48e0 fp =3D 0xffff000103ea4940 pmap_protect() at vm_map_protect+0x2ec pc =3D 0xffff00000070f4d0 lr =3D 0xffff0000006ae188 sp =3D 0xffff000103ea4950 fp =3D 0xffff000103ea49b0 vm_map_protect() at sys_mprotect+0x58 pc =3D 0xffff000 sp =3D 0xffff000103ea49c0 fp =3D 0xffff000103ea= 49c0 sys_mprotect() at do_el0_sync+0x4fc pc =3D 0xffff0000006b3758 lr =3D 0xffff000000717c58 sp =3D 0xffff000103ea49d0 fp =3D 0xffff000103ea4a70 do_el0_sync() at handle_el0_sync+0x84 pc =3D 0xffff000000717c58 lr =3D 0xffff0000006fea00 sp =3D 0xffff000103ea4a80 fp =3D 0xffff000103ea4b90 handle_el0_sync() at 0x43a83c pc =3D 0xffff0000006fea00 lr =3D 0x000000000043a83c sp =3D 0xffff000103ea4ba0 fp =3D 0x0000fffffffee930 The panic does not happen on a NODEBUG kernel and nothing bad seems to happ= en after that :) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237435-7>