[Bug 208138] process freezes in STOP state and can't be killed
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Mar 19 14:44:09 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208138
Bug ID: 208138
Summary: process freezes in STOP state and can't be killed
Product: Base System
Version: 10.2-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: threads
Assignee: freebsd-threads at FreeBSD.org
Reporter: robert.ayrapetyan at gmail.com
CC: freebsd-amd64 at FreeBSD.org
CC: freebsd-amd64 at FreeBSD.org
Hello!
I've started to observe a very strange behavior on my desktop PC (never seen
anything like that using FreeBSD as a desktop OS for more than 5 years).
Two things changed since I've started to observe problems:
1. A new PC (HP Z440) setup
2. Updated OS (FreeBSD 10.2)
At some moment some process freezes and can't be killed\removed.
So far this happened with firefox, thunderbird and virtualbox.
Only OS restart helps to remove such process from a list.
It's a really annoying to have e.g. multiple firefox tabs in the panel which
are dead.
Details are given below:
>uname -a
FreeBSD work-pc 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu Jan 14 01:32:46
UTC 2016 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64
>uname -UK
1002000 1002000
>ps aux | grep firefox
robert 1022 0.0 4.1 1102920 676568 v0 T Mon03PM 101:01.17
firefox -profile /portable/firefox/robert
>procstat -k 1022
PID TID COMM TDNAME KSTACK
1022 100281 firefox Timer mi_switch sleepq_timedwait_sig
_sleep umtxq_sleep do_wait __umtx_op_wait_uint_private amd64_syscall
Xfast_syscall
1022 100428 firefox DOM Worker mi_switch thread_suspend_switch
thread_single exit1 sigexit postsig ast Xfast_syscall
>procstat -i 1022
PID COMM SIG FLAGS
1022 firefox HUP --C
1022 firefox INT --C
1022 firefox QUIT -I-
1022 firefox ILL --C
1022 firefox TRAP ---
1022 firefox ABRT --C
1022 firefox EMT ---
1022 firefox FPE -I-
1022 firefox KILL ---
1022 firefox BUS ---
1022 firefox SEGV --C
1022 firefox SYS ---
1022 firefox PIPE -I-
1022 firefox ALRM ---
1022 firefox TERM P--
1022 firefox URG -I-
1022 firefox STOP ---
1022 firefox TSTP ---
1022 firefox CONT ---
1022 firefox CHLD -I-
1022 firefox TTIN ---
1022 firefox TTOU ---
1022 firefox IO -I-
1022 firefox XCPU ---
1022 firefox XFSZ ---
1022 firefox VTALRM --C
1022 firefox PROF ---
1022 firefox WINCH -I-
1022 firefox INFO -I-
1022 firefox USR1 ---
1022 firefox USR2 ---
1022 firefox 32 --C
...
1022 firefox 65 --C
1022 firefox 66 --C
1022 firefox 67 --C
pkill CONT 1022
pkill KILL 1022
produces no effect.
There are no new messages in /var/log/messages.
More info (stacks for 2 threads behind STOPped process 1022)
(kgdb) thread 337
[Switching to thread 337 (Thread 100281)]#0 sched_switch (
td=0xfffff800b429d000, newtd=<value optimized out>,
flags=<value optimized out>) at /usr/src/sys/kern/sched_ule.c:1945
1945 cpuid = PCPU_GET(cpuid);
(kgdb) bt
#0 sched_switch (td=0xfffff800b429d000, newtd=<value optimized out>,
flags=<value optimized out>) at /usr/src/sys/kern/sched_ule.c:1945
#1 0xffffffff80952121 in mi_switch (flags=517, newtd=0x0)
at /usr/src/sys/kern/kern_synch.c:491
#2 0xffffffff80990deb in sleepq_timedwait_sig (wchan=<value optimized out>,
pri=<value optimized out>) at /usr/src/sys/kern/subr_sleepqueue.c:578
#3 0xffffffff80951af8 in _sleep (ident=0xfffff80011bd7400,
lock=0xffffffff815c6ee0, priority=<value optimized out>,
wmesg=0xffffffff80fcb076 "uwait", sbt=<value optimized out>,
pr=<value optimized out>, flags=<value optimized out>)
at /usr/src/sys/kern/kern_synch.c:249
#4 0xffffffff80966195 in umtxq_sleep (uq=0xfffff80011bd7400,
wmesg=0xffffffff80fcb076 "uwait", abstime=0xfffffe0464912900)
at /usr/src/sys/kern/kern_umtx.c:780
#5 0xffffffff80969007 in do_wait (td=<value optimized out>,
addr=<value optimized out>, id=<value optimized out>,
timeout=<value optimized out>, compat32=<value optimized out>,
is_private=<value optimized out>) at /usr/src/sys/kern/kern_umtx.c:1247
#6 0xffffffff8096d473 in __umtx_op_wait_uint_private (
td=<value optimized out>, uap=<value optimized out>)
at /usr/src/sys/kern/kern_umtx.c:3494
#7 0xffffffff80d4b3e7 in amd64_syscall (td=0xfffff800b429d000, traced=0)
at subr_syscall.c:134
---Type <return> to continue, or q <return> to quit---
#8 0xffffffff80d30acb in Xfast_syscall ()
at /usr/src/sys/amd64/amd64/exception.S:396
#9 0x000000080119fe1c in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) thread 338
[Switching to thread 338 (Thread 100428)]#0 sched_switch (
td=0xfffff801108324a0, newtd=<value optimized out>,
flags=<value optimized out>) at /usr/src/sys/kern/sched_ule.c:1945
1945 cpuid = PCPU_GET(cpuid);
(kgdb) bt
#0 sched_switch (td=0xfffff801108324a0, newtd=<value optimized out>,
flags=<value optimized out>) at /usr/src/sys/kern/sched_ule.c:1945
#1 0xffffffff80952121 in mi_switch (flags=266, newtd=0x0)
at /usr/src/sys/kern/kern_synch.c:491
#2 0xffffffff80959e00 in thread_suspend_switch (td=0xfffff801108324a0,
p=0xfffff800112a8000) at /usr/src/sys/kern/kern_thread.c:947
#3 0xffffffff809599f5 in thread_single (p=0xfffff800112a8000, mode=1)
at /usr/src/sys/kern/kern_thread.c:740
#4 0xffffffff8090c75e in exit1 (td=0xfffff801108324a0, rv=15)
at /usr/src/sys/kern/kern_exit.c:244
#5 0xffffffff8094bf85 in sigexit (td=0xfffff801108324a0, sig=15)
at /usr/src/sys/kern/kern_sig.c:2974
#6 0xffffffff8094c826 in postsig (sig=<value optimized out>)
at /usr/src/sys/kern/kern_sig.c:2877
#7 0xffffffff809959c7 in ast (framep=<value optimized out>)
at /usr/src/sys/kern/subr_trap.c:281
#8 0xffffffff80d30b30 in Xfast_syscall ()
at /usr/src/sys/amd64/amd64/exception.S:421
#9 0x000000080146e64a in ?? ()
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-amd64
mailing list