[Bug 192825] Continual Core Dumps vm_page_unwire: wire count is zero

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192825 Masse Nicolas changed: What|Removed |Added CC||nicolas.masse@stormshield.e

[Bug 192825] Continual Core Dumps vm_page_unwire: wire count is zero

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192825 --- Comment #4 from Masse Nicolas --- FYI : (kgdb) f 14 #14 0x807d0836 in vm_page_unwire (m=0xfe00d91e90c8, activate=1) at ../../../vm/vm_page.c:2219 2219../../../vm/vm_page.c: No such file or directory. in ../../../vm/v

[Bug 192825] Continual Core Dumps vm_page_unwire: wire count is zero

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192825 --- Comment #5 from Michelle Sullivan --- Nicolas: Single or multiple CPU? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list htt

[Bug 200553] uniq does not support -c with -u -d

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200553 jus...@specialbusservice.com changed: What|Removed |Added Severity|Affects Only Me |Affects Some People

[Bug 192825] Continual Core Dumps vm_page_unwire: wire count is zero

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192825 --- Comment #6 from Masse Nicolas --- Multiple (one quadcore-cpu to be exact) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list

[Bug 192825] Continual Core Dumps vm_page_unwire: wire count is zero

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192825 --- Comment #7 from Michelle Sullivan --- Probably not going to help you then, but I have found that switching to a single CPU stops the panics. >From my investigations the ARC/metadata will blow out the kmem until it's exhausted on multip

[Bug 198149] [hwpmc] pmcstat -P -t (top mode, process sampling) stops after a while

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198149 --- Comment #17 from commit-h...@freebsd.org --- A commit references this bug: Author: jhb Date: Mon Jun 1 18:08:58 UTC 2015 New revision: 283886 URL: https://svnweb.freebsd.org/changeset/base/283886 Log: MFC 283123: Fix two bugs that

[Bug 198912] [base/release/10.1.0/contrib/file][security] Multiple Vulnerabilities

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198912 Xin LI changed: What|Removed |Added CC||delp...@freebsd.org Assignee|fr

[Bug 200580] superfluous/unnecessary endhostent() does close(0) by accident. libc resolver dns fd close

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200580 Bug ID: 200580 Summary: superfluous/unnecessary endhostent() does close(0) by accident. libc resolver dns fd close Product: Base System Version: 10.1-RELEASE Hardware

[Bug 200585] [nlm] Fatal trap 9 when printing out KASSERT trying to run umount -f on an NFS share while it's trying to print out "lockd not responding" in nlm(4)

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200585 Garrett Cooper,425-314-3911 changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.or

[Bug 200585] [nlm] Fatal trap 9 when printing out KASSERT trying to run umount -f on an NFS share while it's trying to print out "lockd not responding" in nlm(4)

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200585 Bug ID: 200585 Summary: [nlm] Fatal trap 9 when printing out KASSERT trying to run umount -f on an NFS share while it's trying to print out "lockd not responding" in nlm(4)

[Bug 200587] panic: vinvalbuf: dirty bufs

2015-06-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200587 Bug ID: 200587 Summary: panic: vinvalbuf: dirty bufs Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects