In article <422BAC46.90001@lundman.net>,
Jorgen Lundman  <lundman@lundman.net> wrote:
>
>I can now confirm this happens in NetBSD-2.0 as well. Nonblocking listen(2) 
>socket, that stalls forever. kill -9 does not terminate process. If I want that 
>port back, I have to reboot. (Unless there is some way I can hack/claim it back 
>with gdb+kernel?). The rest of the machine is just fine.
>
>deadlocked due to IO when its a disk I understand, but the same based on
>network?
>
>Still only happens every 40 days or so, so it is hard to track down. I can not 
>run ktrace that long since it logs all the data as well. (Can one tell
>ktrace to 
>only record the call, not the data?)
>
>Could I force a dump at this time, since the machine itself it working fine, to 
>further investigate the trouble?

What wait channel is the process stuck on (ps -axl)?

christos