On Mon, Jul 13, 2015 at 11:12:05PM +0200, Pawel Pekala wrote: > Hi > > I'm getting 100% reproducible kernel crash while trying build ports > with poudriere on my system. This started to show up about 2-3 weeks > ago. I upgrade my system on weekly basis usually on saturday. > Here's backtrace: > > (kgdb) bt [..] > at /hdd/src/sys/amd64/amd64/trap.c:201 > #25 0xffffffff80dace32 in calltrap () at /hdd/src/sys/amd64/amd64/exception.S:235 > #26 0xffffffff80941430 in knote (list=0xfffff801a2589408, hint=2147483648, > lockflags=<value optimized out>) at /hdd/src/sys/kern/kern_event.c:1920 > #27 0xffffffff80946a51 in exit1 (td=0xfffff801b84014d0, rv=<value optimized out>) > at /hdd/src/sys/kern/kern_exit.c:560 > #28 0xffffffff80945f1e in sys_sys_exit (td=0x0, uap=<value optimized out>) > at /hdd/src/sys/kern/kern_exit.c:178 > #29 0xffffffff80dcdaa2 in amd64_syscall (td=0xfffff801b84014d0, traced=0) > at subr_syscall.c:133 > #30 0xffffffff80dad11b in Xfast_syscall () at /hdd/src/sys/amd64/amd64/exception.S:395 > #31 0x0000000800922eea in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > > Let me know if you need more details. Well, if the problem is really that reproducible it would be best if you narrowed it down to the exact commit. However, quick look suggests you may be a "victim" of r284861. Can you enter kgdb and: f 26 p *list ? -- Mateusz Guzik <mjguzik gmail.com>Received on Mon Jul 13 2015 - 19:28:26 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:58 UTC