Interpreting ERROR!!! Calling xxx_SetProcPermissions in Wince 6.0 with platman 'cepermon' tool

I'm working on an SoC architecture where various drivers and user
application code need to share access to the specialized hardware
coherently. For example, the state video subsystem must be identically
viewed by all clients - display drivers, dshow filters, etc.

To implement this, I wrapped the hardware libraries in a device driver,
using IOCTLs to marshall bits in from user mode. Works like a champ.

However, now when I run the Remote Performance Monitor tool, I get a fairly
rich spew of messages out the debug port when using the driver.
137392 PID:4cc0002 TID:5310002 ERROR!!! Calling xxx_SetProcPermissions
137696 PID:4cc0002 TID:5310002 ERROR!!! Calling xxx_SetProcPermissions
138404 PID:4cc0002 TID:5310002 ERROR!!! Calling xxx_SetProcPermissions
138707 PID:4cc0002 TID:5310002 ERROR!!! Calling xxx_SetProcPermissions
139414 PID:4cc0002 TID:5310002 ERROR!!! Calling xxx_SetProcPermissions
139780 PID:4cc0002 TID:5310002 ERROR!!! Calling xxx_SetProcPermissions
140424 PID:4cc0002 TID:5310002 ERROR!!! Calling xxx_SetProcPermissions
140828 PID:4cc0002 TID:5310002 ERROR!!! Calling xxx_SetProcPermissions
141435 PID:4cc0002 TID:5310002 ERROR!!! Calling xxx_SetProcPermissions
or roughly every 300 msec while viewing any one of a number of parameters
including CE processor Statistics/% processor time

This is on a build where only the display driver is accessing the hardware
device driver. Altering the build so that the display drier is linked to a
KM DLL exporting the APIs directly, the messages go away.

Anyone have a clue what the origin/interpretation of this message is?

--Richard R. Lee eMVP


.

Relevant Pages

  • [origin tree SLAB corruption] BUG kmalloc-64: Poison overwritten, INFO: Allocated in bdi_alloc_w
    ... Bus #0 is PCI ... Performance Counters: AMD PMU driver. ... initcall migration_init+0x0/0x69 returned 0 after 3255 usecs ... calling spawn_ksoftirqd+0x0/0x69 @ 1 ...
    (Linux-Kernel)
  • Re: How to call function from driver in inline assembler
    ... It seems that in calling by this way must be prepared ebx register? ... Or not possible to call other functions than are part of calling driver? ... Yes I agree with you that using inline _asm is not very effective ... push 0x48c ...
    (microsoft.public.development.device.drivers)
  • Re: [PATCH] call drv->shutdown at rmmod
    ... Patrick Mochel writes: ... >> device shutdown method at module remove time, in addition to calling ... > could also be extended to include a power state, ... Assuming the device driver can get a device out of the suspend state ...
    (Linux-Kernel)
  • Re: bugcheck during unload
    ... The bugcheck parameters (and by the ... >>>>why ndisHandleProtocolUnbindNotification is calling ... >>>I came across a minidump for a crash in my NDIS IM driver. ...
    (microsoft.public.development.device.drivers)
  • Re: Drivers for SBS 2003
    ... Any driver for Windows 2003 (non-64 bit) will work. ... Now, more importantly, what hardware are you trying to find drivers for? ... Calling an illegal alien an "undocumented worker" is like calling a ...
    (microsoft.public.windows.server.sbs)