Thanks again for your help. A few items:
1. Separate -- You're right, i had --separate=all. I've modified it to what you recommend (--separate=lib,kernel). Now i no longer need the --merge tgid
2. Image Path -- I tried using --image-path=/lib/modules/`uname -r` and then did "lsmod" to see which modules were running. Running the opreport command searching for one of the modules (say, "ipv6") seem to return nothing. When i tried --image-path=/lib/modules/`uname -r`/kernel, then it would return something like:
samples % image name symbol name
1 100.000 ipv6.ko fib6_walk
Does this mean i should use the /kernel ? Might be because i'm on Centos 6.3?
3. VMLinux -- When i ran the opcontrol command, i used the --vmlinux= command to specify a vmlinux file. This file was generated before i compiled and installed the custom kernel module (i did not build the module inside the 3.2 kernel source tree.. nor did i "add" it to the kernel .config or build system). I'm wondering if this is perhaps the cause of not being able to "see" my kernel module (i.e., the "old" vmlinux doesn't have the correct symbols to process this?). In this case, would running it with --no-vmlinux, and then running the "opsymbols.rb" ruby script (which i think looks at /proc/kallsyms for symbols) find my custom kernel module? When i "cat /proc/kallsyms", my custom kernel module is listed with all the symbols.
If its better just to recompile vmlinux, do you happen to know any good links/tutorials on how to "add" new custom modules to the kernel build system?