Date: Tue, 26 Jan 2016 05:27:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 206634] panic: ncllock1 after NFSv4 server was taken offline and brought back to life; lots of spam about Message-ID: <bug-206634-8@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206634 Bug ID: 206634 Summary: panic: ncllock1 after NFSv4 server was taken offline and brought back to life; lots of spam about Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ngie@FreeBSD.org Created attachment 166130 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=166130&action=edit Panic screenshot from IPMI A FreeBSD 11.0-CURRENT NFSv4 client with a GENERIC-NODEBUG kernel panicked with `panic: ncllock1` after the NFSv4 server it was connected to was brought offline, then brought back to life. I've attached some screenshots. Unfortunately I can't get a dump because my swap device is too small :(... The last built kernel/world was from this github revision: commit ec77f0bef381d18a7cb6847d3e0f02c0f4087f05 Author: imp <imp@FreeBSD.org> Date: Tue Jan 5 21:20:47 2016 +0000 Use the more proper -f. Leave /bin/rm in place since that's what other rc scripts have, though it isn't strictly necessary. Notes: svn path=/head/; revision=293227 The machine's still up -- please let me know if there's anything I can grab to help with debugging this issue. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206634-8>