topic Re: a bad primitive in Operating System - HP-UX

a bad primitive

Leo Wong_1 — Wed, 17 Mar 2004 05:27:11 GMT

when i type dmesg, i got the below message.

Received a bad primitive: prim is 35
Received a bad primitive: prim is 35
Received a bad primitive: prim is 35
Received a bad primitive: prim is 35
Received a bad primitive: prim is 35
Received a bad primitive: prim is 35

Please help where the problem is

Re: a bad primitive

G. Vrijhoeven — Wed, 17 Mar 2004 05:54:26 GMT

Hi,

I only found a pdf that describes the problem. Here is the link:

http://sctpixel.home.cern.ch/sctpixel/MessageProtocol/MessageProtocolV25.pdf

HTH,

Gideon

Re: a bad primitive

Floyd Curtis — Wed, 17 Mar 2004 07:49:10 GMT

Check /var/adm/syslog/syslog.log or OLDsyslog.log to see if there is more information. dmesg info is sometimes not as complete as well as not being timestamped.

Look at when the error occured to give you some hints as to what programs/processes may have been running at the time as well as where the error came from.
If there is leading info on line after a timestamp, it will sometimes tell you what subsystem logged the error... i.e vmunix, rpcbind, inetd, syslog. Anything logged by syslog could even be external to the system.

good luck,
fwc

Re: a bad primitive

Leo Wong_1 — Wed, 17 Mar 2004 22:40:28 GMT

Gideon,

Thanks. I still can't find out what prim 35 means. Anyway to decode it.

Leo

Re: a bad primitive

Bill Hassell — Wed, 17 Mar 2004 22:55:45 GMT

This is an example of a bad error message. It was reported to the console (and logged into the kernel message buffer, dmesg reports what is there) but there is no clue as to the name of the program. Because there is no program info, you'll have search through syslog to see if anything else is there. If not, you'll have to stop all your applications and then start them one by one until the messages start occurring.

Re: a bad primitive

Leo Wong_1 — Wed, 17 Mar 2004 23:13:39 GMT

I capture more for it. Does it mean sr_send2db and sr_putstop programe problem.

WARNING: sr_send2bd: dtiB3T18 not ready for command!
WARNING: sr_send2bd: dtiB3T4 not ready for command!
WARNING: sr_send2bd: dtiB3T14 not ready for command!
WARNING: sr_send2bd: dtiB3T19 not ready for command!
WARNING: sr_putstop: dtiB3T3 not ready for command!
WARNING: sr_putstop: dtiB3T19 not ready for command!
WARNING: sr_send2bd: dtiB3 not ready for command!
Received a bad primitive: prim is 35
Received a bad primitive: prim is 35
Received a bad primitive: prim is 35
Received a bad primitive: prim is 35
Received a bad primitive: prim is 35
Received a bad primitive: prim is 35

Re: a bad primitive

Bill Hassell — Thu, 18 Mar 2004 08:44:49 GMT

Google is amazing! I put in the keyword sr_putstop and got this in 2 seconds:

Defect Description:
PHNE_23784:
Driver times out while waiting for board to get ready.
Driver logs following messages to syslog:
WARNING: sr_send2bd: dxxxB24C2 not ready for command!
WARNING: sr_putstop: dxxxB24C2 not ready for command!
Resolution:
Fix sr_send2bd() and sr_putstop() by increasing timeout from
1 second to 10 seconds.

This is an Xwindows problem. It sounds like your patches are not current. Since this patch is for 10.20 (obsolete and unsupported), you would do well to download he last two patch bundles (QPK and HWE) for Dec 2001, the last set of patche bundles for 10.20.

Re: a bad primitive

Bill Hassell — Thu, 18 Mar 2004 08:47:12 GMT

Sorry, I was looking at another patch. It's for the VoiceLink product, not Xwindows.

Re: a bad primitive

Leo Wong_1 — Thu, 18 Mar 2004 22:53:44 GMT

Bill, Good job. You have resolved my problem.