From: Andreas D. L. <ad...@tz...> - 2005-07-08 13:15:28
|
... I had the same problem and some time ago and Pat had the answer: Patrick Riley wrote: > I'll take a guess and say you didn't follow this step of the perfctr > install: > > DEVICE FILE > ----------- > The kernel-side of this package is implemented as a character device > driver, which has been assigned major number 10 and minor number 182. > The first time you install the package, a special file representing > this device must be created. As root, execute: > > mknod /dev/perfctr c 10 182 > chmod 644 /dev/perfctr > > If the driver was built as a module, it will be have to be loaded > into the kernel before it can be used. This will happen automatically > if the kernel was built with support for the kernel module loader > (CONFIG_KMOD=y). For 2.6 kernels no further action is needed. For > 2.4 kernels, the following should be added to /etc/modules.conf: > > alias char-major-10-182 perfctr > Best regards, Andreas Lattner (Virtual Werder 3D) so...@ce... wrote: > Dear All, > I have installed the perfctr kernel patch on my Gentoo machine. When I run > the rcssserver3D, I get the following error messages for all agent > pids(e.g. 3363 below): > > "EngineError(0): PerfCtrFD::fdOpenSelf: open failed 2 No such file or > directory > EngineError(0): PerfCtrFD::openControlSend: failed openSelf > EngineError(0): ProcessTimer_PerfCtrInstr::setupPostForkPreExec: failed > openControlSend > EngineError(0): ProcessTimer_PerfCtrInstr::prot_notifyAddPid: did not > receive fd for pid 3363 > EngineWarning[10](0): Subclass rejected adding the pid 3363 > E" > > But after that the server is up and all agents are ok. > What is the problem? > If the perfctr timer fails to initialize then which timer is used during > the simulation?(Is it default?) > > My machine configuration is: > -Gentoo Linux(kernel 2.6.11-gentoo-r11) > -perfctr 2.6.14 > -Spades 1.10 > -"perfctr_instr 10000" in agentdb.xml > > Regards, > Mojtaba Solgi > |