NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/49530: kernel crash with corrupt stack/invalid backtrace

The following reply was made to PR kern/49530; it has been noted by GNATS.

From: Martin Husemann <>
Subject: Re: kern/49530: kernel crash with corrupt stack/invalid backtrace
Date: Sat, 10 Jan 2015 11:30:41 +0100

 And again a crash from the vdrain thread:
 db{0}> mach stack
 Window 0 frame64 0x1b027ba80 locals, ins:
 103b458c0 1b0278000 ffffffffffffffff 1b027bed0 1c6f988 1b018a000 e0048000 e0048000
 1052190a0 20002 10 4 1048bb008 174b7a0 1b027b351=sp 156eefc=pc:netbsd:vn_lock+0x7c
 Window 1 frame64 0x1b027bb50 locals, ins:
 1832b50 17adac0 17adaf8 17adaf8 1818338 17adaf8 17adac0 0
 1052190a0 20002 103b558e0 1ce4400 1048bb008 0 1b027b401=sp 156ade4=pc:netbsd:vcl
 Window 2 frame64 0x1b027bc00 locals, ins:
 0 0 0 0 17e8d68 17adaf8 17adac0 17c0f80  
 1052190a0 103b558e0 103b558e0 0 103b558e0 1 1b027b4c1=sp 156c4dc=pc:netbsd:cleanvnode+0x13c
 Window 3 frame64 0x1b027bcc0 locals, ins:
 17adaf8 17adac0 1832fb8 1832e38 0 17adaf8 17adac0 17c0f80
 0 1832ce8 1c95400 1c95740 1c95740 1052190a0 1b027b571=sp 156c6a4=pc:netbsd:vdrain_thread+0x84
 Window 4 frame64 0x1b027bd70 locals, ins:
 103b44420 1b0278000 deaddead 1b027bed0 1c6f988 1b0270000 e0048000 e0048000
 1c956c0 1832ff8 1c0a1fc 1c957c0 1c0a1e8 1c95780 1b027b621=sp 1011fb8=pc:netbsd:lwp_trampoline+0x8
 Sounds to me like a somehow corrupted vnode on the cleanlist?
 The crash happens in vn_lock() when calling VOP_LOCK(), probably the
 	error = (VCALL(vp, VOFFSET(vop_lock), &a));
 going wrong. Is there an easy way to assert that the vop_lock points to
 a kernel text address?

Home | Main Index | Thread Index | Old Index