[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #31 from Rick Macklem --- And thanks go to you for doing the testing and commits. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Andriy Gapon changed: What|Removed |Added Status|In Progress |Closed

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #29 from commit-h...@freebsd.org --- A commit references this bug: Author: avg Date: Tue Feb 21 09:29:47 UTC 2017 New revision: 314034 URL: https://svnweb.freebsd.org/changeset/base/314034 Log: MFC r313735: add svcpool_close

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #28 from commit-h...@freebsd.org --- A commit references this bug: Author: avg Date: Tue Feb 21 09:29:11 UTC 2017 New revision: 314033 URL: https://svnweb.freebsd.org/changeset/base/314033 Log: MFC r313735: add svcpool_close

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #27 from commit-h...@freebsd.org --- A commit references this bug: Author: avg Date: Tue Feb 14 17:49:08 UTC 2017 New revision: 313735 URL: https://svnweb.freebsd.org/changeset/base/313735 Log: add svcpool_close to handle

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #26 from Andriy Gapon --- (In reply to Rick Macklem from comment #25) Rick, thank you very much! We tested this patch and it makes nfsd more robust with respect to SIGKILL. We haven't seen any regressions. --

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Rick Macklem changed: What|Removed |Added Attachment #179512|0 |1 is

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Rick Macklem changed: What|Removed |Added Status|Closed |In Progress

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #23 from Rick Macklem --- Created attachment 179512 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179512=edit add svcpool_close so that svcpool_destroy doesn't get called when nfsd threads are

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #22 from Andriy Gapon --- (In reply to Rick Macklem from comment #20) Rick, thank you very much for the explanation! I knew that nfsd processes were special as they 'lend their stacks to kernel' or something

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #21 from Rick Macklem --- Oh, and if you get a crash when shutting down the nfsd threads via "kill -USR1 ", then let us know, since something is still broken. (If you are curious, the "(master)" nfsd is

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #20 from Rick Macklem --- Well, you should never kill the nfsd with SIGKILL. The way that is intended to be "safe" is to send SIGUSR1 to the "(master)" nfsd. It will shut things down and kill off the other

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #19 from Andriy Gapon --- (In reply to Rick Macklem from comment #18) > Andriy Gapon, did your crash occur when the machine was being shut down (or the nfsd threads were being killed off)? Yes, it did. I am

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #18 from Rick Macklem --- Andriy Gapon, did your crash occur when the machine was being shut down (or the nfsd threads were being killed off)? If not, it is not caused by what these patches were intended

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Andriy Gapon changed: What|Removed |Added CC||a...@freebsd.org

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Rick Macklem changed: What|Removed |Added Resolution|--- |FIXED

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Rick Macklem changed: What|Removed |Added Flags|mfc-stable10? |mfc-stable10+

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #12 from g_amana...@yahoo.com --- The three last patches resolve the bug. @rick thank you. @koobs MFC? -- You are receiving this mail because: You are on the CC list for the bug. ___

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #14 from Rick Macklem --- Also, although it was good to get this crash resolved, I would recommend trying to avoid doing nfsd thread restarts. (If by any chance you were doing this to avoid access problems

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Rick Macklem changed: What|Removed |Added Flags|mfc-stable9?|mfc-stable9-

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #15 from commit-h...@freebsd.org --- A commit references this bug: Author: rmacklem Date: Sat Nov 21 23:55:46 UTC 2015 New revision: 291150 URL: https://svnweb.freebsd.org/changeset/base/291150 Log: When the nfsd threads are

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #11 from g_amana...@yahoo.com --- I am currently testing with the three last patches applied as I do have NFSv4.1 clients running on Linux. Give me a couple of days and I will provide feedback. Thank you for the insight. --

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Mark Linimon changed: What|Removed |Added Keywords||patch -- You

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #9 from Rick Macklem --- Created attachment 163300 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163300=edit patch that makes NFSv4.1 server release the backchannel xprt This patch fixes the

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #8 from Rick Macklem --- Created attachment 163299 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163299=edit patch that locks mutex when request queue is updated This patch fixes the only

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #10 from Rick Macklem --- I have just added 2 more patches that might be relevant to the crashes. When the nfsd threads are terminated, this is what is supposed to happen: - All nfsd threads running in

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #5 from g_amana...@yahoo.com --- (In reply to Rick Macklem from comment #4) I am testing it, so far it seems ok. Give me a couple of days to test it thoroughly. -- You are receiving this mail because: You are on the CC list

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #6 from g_amana...@yahoo.com --- (In reply to Rick Macklem from comment #4) It still crashes. I am going to get a dump tomorrow. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #7 from g_amana...@yahoo.com --- This a fresh dump with the second patch applied, it seems the same. The problem seems to occur in xprt_active(). Unread portion of the kernel message buffer: stack pointer =

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable9?,

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #3 from g_amana...@yahoo.com --- (In reply to Rick Macklem from comment #2) Thanks for the insight. However, I just tried the patch proposed and it still crashes. -- You are receiving this mail because: You are on the CC list

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Rick Macklem changed: What|Removed |Added Attachment #163160|0 |1 is

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Rick Macklem changed: What|Removed |Added Status|New |In Progress

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Sean Bruno changed: What|Removed |Added Keywords||IntelNetworking

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 g_amana...@yahoo.com changed: What|Removed |Added CC||freebsd-bugs@FreeBSD.org --

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Bug ID: 204340 Summary: [panic] nfsd, em, msix, fatal trap 9 Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity:

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 g_amana...@yahoo.com changed: What|Removed |Added Hardware|Any |amd64 CC|

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #1 from g_amana...@yahoo.com --- Setting hw.em.enable_msix=0 in bootloader.conf resolves the symptoms. -- You are receiving this mail because: You are the assignee for the bug. ___