Date: Wed, 23 Apr 1997 02:58:05 +1000 From: Bruce Evans <bde@zeta.org.au> To: current@freebsd.org Subject: init sleeping on "thrd_s" Message-ID: <199704221658.CAA26529@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
My vfork debugging problems seem to have been caused by vm_map problems.
The problems somehow got all the way back to init. Everything not related
to the hung processes seems to work perfectly.
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.37 (swapper)
0 1 0 0 -18 0 184 132 thrd_s Ds ?? 0:00.52 /sbin/init -
...
15 190 1 0 28 0 0 0 - Z v0- 0:00.00 (bash)
...
15 7403 1 0 -18 0 440 0 thrd_s DE v3- 0:00.00 (csh)
15 7742 7403 2 28 0 0 0 - Z v3- 0:00.00 (sh)
15 8334 1 0 -18 0 440 0 thrd_s DE v3- 0:00.00 (csh)
15 8336 8334 3 28 0 0 0 - Z v3- 0:00.00 (sh)
15 8846 1 1 -6 0 0 0 - Z v3- 0:00.00 (bash)
15 8916 1 0 -18 0 440 0 thrd_s DE v3- 0:00.00 (csh)
15 8917 8916 4 29 0 0 0 - Z v3- 0:00.00 (sh)
15 8918 1 0 10 0 248 316 wait S v3- 0:02.38 /bin/sh /tmp
More debugging problems:
- "thrd_s" doesn't uniquely determine the code that is sleeping.
This seems to be hard to fix. It's probably too inefficient to pass
unique strings to lockmgr().
- "thrd_s" is poorly named. Sleep message strings are restricted to
6 characters and should be carefully explicitly abbreviated to 6
characters. There is no room for underscores.
Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704221658.CAA26529>