The PTM_CTRL que smells fishy.

[Anonymous]

Hello,

We are experiencing some panics in one of our processes…

The log for the panics reads:   ” The PTM_CTRL que smells fishy. ” 😯

See the log…

Code:

[msg :RecP:DBUG/3:   tm11_xlate] hrSearchAddr: 2(0)
[diag:leak:DBUG/0:   tm11_xlate] diag grmData free  0x13482c8
03/21/2005 12:35:56
[pti :sign:WARN/0:   tm11_xlate] Thread 1 received signal 11
03/21/2005 12:35:56
[pti :sign:WARN/0:   tm11_xlate] PC = 0xffffffff
[pti :thre:INFO/0:   tm11_xlate] Thread 1 was told to shutdown
[diag:leak:DBUG/0:   tm11_xlate] diag ptm alloc 0x1349d40
[pti :msg :DBUG/1:   tm11_xlate] Send PTM 0x1349d40 from 1 to 1: data 0x0
[pti :sche:DBUG/1:   tm11_xlate] The PTM_CTRL que smells fishy.
[msi :msi :INFO/0:   tm11_xlate] Updating shared memory to mark threads as dead.
PANIC: “0”
PANIC: Calling “pti” for thread tm11_cmd
—– Scheduler State —–
Thread Events     State      Priority Runnable  PT Msgs
  0      0   SCHED_IDLE         0       0       0,0,0
  1      0   SCHED_RUNNING      0       0       1,0,0
  2      0   SCHED_IDLE         0       0       0,0,0

————– Thread 0 ————–
ti: 0x601df0
   tid           :    0
   HostPthreadId : 0x1
   EventList     : 0x5ee9e8
   PolledEvents  : 0x5eea00
   PthreadEvent  : 0x6020b8
   ReadyEvents   : 0x5eea18
   CtrlMsgs      : 0x5eea30
   UserCtrlMsgs  : 0x5eea48
   UserDataMsgs  : 0x5eea60
   StartArgs     : 0x0
   SchedState    : SCHED_IDLE
   SchedPriority : 0
   Killed        : 0
—– Registered Events —–

We enabled all the logs to see if we could get more info because the process panics once every one or two days.

With the engine output enabled it was stable for almost a week. It was bouced to clear the log (it was huge) and few minutes later we had the panic.

I’m not sure how to interpret the “smells fishy”

Any help is appreciated.

Topic

[Terry Kellum]

Old versions of Unix had the error message coded into them “lp is on fire” and was activated for an unknown error.  

(You don’t have a night operator cleaning bass in your server room at night do you?)

[Anonymous]

Carlos,

I see the same error for SIGNAL 11.

I posted another thread for this issue on AIX 5.1, QDX 5.3

What’s your QDX version?

What OS are you runnning ?

Thx

Reggie

[Anonymous]

Reggie,

This happened in a Sun Solaris 8.

We have QDX 5.2 with all the patches.

We did something and we don’t get this now. I think what fixed the problem was bouncing the process more often.

Best regards,

Carlos

[Author]

Replies