John Smith wrote:
> We got a problem when we are using OProfile to sample Linux IPv4 with
> some network card driver. After we stopped OProfile and use opreport to
> retrieve the profiling results, OProfile always reports "No Symbols" for
> the NIC driver module (only the kernel functions are listed there). We
> did add the "-g" flag when we build the NIC driver and we can confirm
> all those symbol information is indeed there by using nm tool to dump
> the symbol information from the NIC driver module file.
> We recompiled the kernel and the problem remains. We did test OProfile
> with some small .c programs and OProfile has no problems with this small
> programs. The OProfile version we use is 0.9.1 and the Linux kernel is
> 2.6.9-11 on CentOS 4.1.
> I really appreciate if somebody can shed some light on this issue.
> Thanks a lot,
OProfile might be searching the wrong place for the driver module code.
Is the location of the driver being listed as /driver.ko (in root
I have some write ups describing how OProfile can be used to analyze
kernel modules at:
The folowing write-ups are the ones that you might look at:
Analyzing Kernel Modules Data in OProfile in RHEL3
Analyzing Kernel Modules Data in OProfile in Fedora Core 3/4 and RHEL4
They are specific to Fedora Core 3/4 and RHEL 3/4, but they might be
useful for what you are doing.