Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Feb 2016 12:59:46 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-threads@FreeBSD.org
Subject:   [Bug 200992] proccess won't die in thread_suspend_switch
Message-ID:  <bug-200992-16-uaEdgPcUDk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200992-16@https.bugs.freebsd.org/bugzilla/>
References:  <bug-200992-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=3D200992

Antonio Nikishaev <me.freebsd@lelf.lu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |me.freebsd@lelf.lu

--- Comment #25 from Antonio Nikishaev <me.freebsd@lelf.lu> ---
This bug is rather major.

I'm seeing the same issue with DigitalOcean instances (10.2-RELEASE(!)).
Riak2 nodes randomly hang up every several days.


% uname -a
FreeBSD riak-freebsd-8gb-nyc3-01 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r2866=
66:
Wed Aug 12 15:26:37 UTC 2015=20=20=20=20
root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

% sudo procstat -k 76975
  PID    TID COMM             TDNAME           KSTACK=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
76975 101201 beam.smp         -                mi_switch sleepq_timedwait
_cv_timedwait_sbt amd64_syscall Xfast_syscall=20
76975 101317 beam.smp         -                mi_switch thread_suspend_swi=
tch
thread_single exit1 sigexit postsig ast doreti_ast=20

% ps -auxw -p 76975
USER   PID %CPU %MEM     VSZ     RSS TT  STAT STARTED       TIME COMMAND
riak 76975  0.0 72.1 7524240 6030480  -  T<s  Tue08PM 1707:20.72
/usr/local/lib/riak/erts-5.10.3/bin/beam.smp -scl false -sfwi 500 -P 2560

--=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-200992-16-uaEdgPcUDk>