HP3000-L Archives

November 1997, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jon Diercks <[log in to unmask]>
Reply To:
Jon Diercks <[log in to unmask]>
Date:
Tue, 18 Nov 1997 08:48:14 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
We have a job which is stuck.  SOS/3000 says the process is in a "Signal
timer wait" and the stack trace shows this:

       PC=a.0017470c enable_int+$2c
NM* 0) SP=41846ef0 RP=a.002a8a0c notify_dispatcher.block_current_process+$31c
NM  1) SP=41846ef0 RP=a.002aae88 notify_dispatcher+$264
NM  2) SP=41846e70 RP=a.001a4c20 wait_for_active_port+$ec
NM  3) SP=41846d70 RP=a.001a58a0 receive_from_port+$534
NM  4) SP=41846cf0 RP=a.00348efc extend_receive+$494
NM  5) SP=41846af0 RP=a.001bb2d0 proc_pause+$45c
NM  6) SP=41846970 RP=a.001bbccc PAUSE+$584
NM  7) SP=418467b0 RP=a.001bb714 ?PAUSE+$8
         export stub: ac1.0006ce54
NM  8) SP=418464f0 RP=ac1.00000000
     (end of NM stack)

I have tried :ALTPROC'ing the AID10 process from the DS queue to the CS
queue.  Nothing seems to work in getting the process to resume executing.
Can any of you help me understand what "Signal timer wait" means, and why
the stack trace would show the process "blocked"?  Thanks.

________________________________________________________
Jon Diercks * Systems Manager         Computing Services
[log in to unmask] (PGP available)     Anderson University
http://rowlf.csv.anderson.edu/        1100 East Fifth St
(765)641-4305 * FAX (765)641-3851     Anderson, IN 46012

ATOM RSS1 RSS2