Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: repeated failure to properly shutdown
On Jul 21, 2016 1:08 PM, "J. Hannken-Illjes" <hannken%eis.cs.tu-bs.de@localhost> wrote:
>
>
> > On 21 Jul 2016, at 19:26, coypu%sdf.org@localhost wrote:
> >
> > On Thu, Jul 21, 2016 at 10:15:32AM -0700, bch wrote:
> >> Jul 20 23:55:59 kamloops /netbsd: wapbl_discard() at netbsd:wapbl_discard+0x20c
> >> Jul 20 23:55:59 kamloops /netbsd: vclean() at netbsd:vclean+0x2ae
> > ...
> >> Jul 20 23:55:59 kamloops /netbsd: tmpfs_unmount() at netbsd:tmpfs_unmount+0x2f
> >
> > For some reason this condition is met:
> > wapbl_vphaswapbl(vp)
> >
> > but why?
>
> The contents of this "struct vnode", especially its "v_tag"
> and "v_mount" could help.
I have kernel cores, but I'm not as familiar w/ crash(8) as gdb.
Initial backtrace looks like this:
Crash version 7.99.34, image version 7.99.34.
System panicked: kernel diagnostic assertion "bp->b_freelistindex ==
-1" failed: file "/usr/src/sys/kern/vfs_bio.c", line 334 double free
of buffer? bp=0xfffffe8108689120, b_freelistindex=0
Backtrace from time of crash is available.
_KERNEL_OPT_NARCNET() at 0
?() at fffffe8119892158
vpanic() at vpanic+0x149
cd_play_msf() at cd_play_msf
brelsel() at brelsel+0x5f0
wapbl_discard() at wapbl_discard+0x20c
vclean() at vclean+0x2ae
vgone() at vgone+0x4b
vflush() at vflush+0xcb
tmpfs_unmount() at tmpfs_unmount+0x2f
VFS_UNMOUNT() at VFS_UNMOUNT+0x24
dounmount() at dounmount+0xbc
sys_unmount() at sys_unmount+0x150
syscall() at syscall+0x15b
--- syscall (number 22) ---
7bfd4dc3ddda:
> --
> J. Hannken-Illjes - hannken%eis.cs.tu-bs.de@localhost - TU Braunschweig (Germany)
>
Home |
Main Index |
Thread Index |
Old Index