Date: Thu, 11 Jun 2020 17:20:06 +0200 From: Johan Hendriks <joh.hendriks@gmail.com> To: freebsd-current@freebsd.org Subject: Re: Panic "vm_fault_lookup: fault on nofault entry" amd64 r362008 -> r362045 Message-ID: <ad0ba8ac-7524-87f6-50cf-4a1b3ffd1651@gmail.com> In-Reply-To: <20200611132129.GL48478@kib.kiev.ua> References: <20200611130500.GW1392@albert.catwhisker.org> <20200611132129.GL48478@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Op 11-06-2020 om 15:21 schreef Konstantin Belousov: > On Thu, Jun 11, 2020 at 06:05:00AM -0700, David Wolfskill wrote: >> Build machine (mini-tower) performed the update (r362008 -> r362045) >> without issue, but my laptop panicked quite early on -- before the dump >> device was configured. >> >> I have taken and placed a couple of screen shots in >> http://www.catwhisker.org/~david/FreeBSD/head/r362045/ >> >> Looking at the displayed backtrace, I see: >> >> --- trap 0xc ... >> futex_xchgl_reslover() >> elf_reloc_internal() >> link_elf_reloc_local() >> link_elf_link_preload_finish() >> linker_preload() >> mi_startup() >> >> Any clues? I'm hapy to poke at it or try patches. >> >> Booting from kernel.old (r362008) still works: >> FreeBSD g1-55.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #46 r362008M/362008: Wed Jun 10 04:19:33 PDT 2020 root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1300097 1300097 > The link times out. > > There is not much to access in futex_xchgl_resolver() except for the > data segment. Without full panic message and disassemble of your instance > of futex_xchgl_resolver() it is not possible to ee what is going on. > > Just in case, can you try clean build, if you did -DNO_CLEAN ? > Just a me too. I updated from 362042 -> 362053 I get this panic very early. (hand typed so could contain some typo's) FreeBSD clang version 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-rc1-0-gf79cd71e145 VT(vgs): resolution 640x480 kernel trap 12 with interupts disabled panic: vm_fault_lookup: fault on nofault entry, addr: 0xffffffff83a3d000 cpuid = 0 time = 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff83a65830 vpanic() at vpanic+0x182/frame 0xffffffff83a65880 panic() ata panic+0x43/frame 0xffffffff83a658e00 vm_fault() at vm_fault+0x1ab5/frame 0xffffffff83a659f0 vm_fault_trap() at vam_fault_trap+0x6-/frame 0xffffffff83a65a30 trap_pfault at trap_pfault+0x19c/frame 0xffffffff83a65a80 trap() at trap+0x271/frame 0xffffffff8365b90 calltrap() at calltrap+0x8/frame 0xffffffff83a65b90 --- trap 0xc, rip = 0xffffffff83a3d470, rsp = 0xffffffff83a65c68, rbp = 0xffffffff83a65cb0 --- opensolaris_utsname_init() at opensolaris_utsname_init/frame 0xffffffff83a65cb0btext() at btext+0x2c KDB: enter : panic [ thread pid 0 tid 0 ] Stopped at kdb_enter+0x37: movq $0,0x1fc1686(%rip) db> > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ad0ba8ac-7524-87f6-50cf-4a1b3ffd1651>