Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Apr 2018 19:17:03 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 227749] post-panic assertion failed: panic: Assertion (*xp & ~LK_EXCLUSIVE_SPINNERS) == LK_SHARERS_LOCK(1) failed at /usr/src/sys/kern/kern_lock.c:541
Message-ID:  <bug-227749-227-K8ZwOY9f8z@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-227749-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-227749-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227749

Conrad Meyer <cem@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|bugs@FreeBSD.org            |cem@freebsd.org
             Status|New                         |Closed
         Resolution|---                         |FIXED

--- Comment #11 from Conrad Meyer <cem@freebsd.org> ---
At least the secondary panic preventing dump is resolved.  It does seem lik=
e a
mistake for dump code to be invoking lockmgr, and Mark's guess that it is a
filesystem buffer completion seems logical to me.

We do have a patch to avoid completing non-dump IO in CAM during coredump. =
 I
don't think we need this PR to track upstreaming that.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227749-227-K8ZwOY9f8z>