Date: Wed, 09 Mar 2016 20:27:39 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-X0zlxC83dD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204426-16@https.bugs.freebsd.org/bugzilla/> References: <bug-204426-16@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=3D204426 --- Comment #63 from Robert Blayzor <rblayzor@inoc.net> --- I have rechecked, recompiled patches against latest 10.3 Now, under normal conditions my dmesg just floods with, thousands of the messages below: pid 3142 kpf 1 pid 3142 kpf 1 pid 3142 kpf 1 pid 3143 kpf 1 pid 3143 kpf 1 pid 3143 kpf 1 pid 3144 kpf 1 pid 3144 kpf 1 pid 3145 kpf 1 pid 3145 kpf 1 pid 3146 kpf 1 pid 3146 kpf 1 pid 3146 kpf 1 pid 3147 kpf 1 pid 3147 kpf 1 pid 3147 kpf 1 pid 3149 kpf 1 pid 3149 kpf 1 pid 3149 kpf 1 pid 3147 kpf 1 pid 3147 kpf 1 pid 3147 kpf 1 pid 3147 kpf 1 pid 3147 kpf 1 pid 3150 kpf 1 pid 3150 kpf 1 pid 3147 kpf 1 pid 3151 kpf 1 pid 3151 kpf 1 pid 3151 kpf 1 pid 3151 kpf 1 pid 3151 kpf 1 pid 3151 kpf 1 ... --=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-204426-16-X0zlxC83dD>