Date: Sat, 8 Aug 2015 17:24:37 -0700 From: Tim Kientzle <tim@kientzle.com> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: Consistent crash of BeagleBone kernel Message-ID: <CC793A5E-83D2-4169-AECB-9690572A00D0@kientzle.com>
index | next in thread | raw e-mail
I’m seeing the following crash quite consistently on r286438. It looks like the recent work on the kernel linker locking still has some issues. Any suggested workarounds? Tim ==== log trace === ... Starting file system checks: /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mmcsd0s2a: clean, 7320851 free (179 frags, 915084 blocks, 0.0% fragmentation) lock order reversal: 1st 0xcd225040 bufwait (bufwait) @ /Users/tim/projects/crochet/src-head/sys/kern/vfs_bio.c:3191 2nd 0xc2e69400 dirhash (dirhash) @ /Users/tim/projects/crochet/src-head/sys/ufs/ufs/ufs_dirhash.c:281 … usual stack trace omitted ... Mounting local file systems:random: unblocking device. . ELF ldconfig path: /lib /usr/lib /usr/lib/compat Setting hostname: beaglebone. Setting up harvesting:[HIGH_PERFORMANCE],[FS_ATIME],SWI,INTERRUPT,NET_NG,NET_ETHER,NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED Feeding entropy:. lock order reversal: 1st 0xc083ef40 kernel linker (kernel linker) @ /Users/tim/projects/crochet/src-head/sys/kern/kern_linker.c:1030 2nd 0xc2d63c94 ufs (ufs) @ /Users/tim/projects/crochet/src-head/sys/kern/vfs_lookup.c:529 KDB: stack backtrace: panic: _sx_xlock_hard: recursed on non-recursive sx kernel linker @ /Users/tim/projects/crochet/src-head/sys/kern/kern_linker.c:552 KDB: enter: panic [ thread pid 168 tid 100079 ] Stopped at $d.7: ldrb r15, [r15, r15, ror r15]! db> bt Tracing pid 168 tid 100079 td 0xc30db6a0 panic: _sx_xlock_hard: recursed on non-recursive sx kernel linker @ /Users/tim/projects/crochet/src-head/sys/kern/kern_linker.c:552 Uptime: 4m0s Rebooting...help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CC793A5E-83D2-4169-AECB-9690572A00D0>