From: Scott D. <sc...@te...> - 2003-03-11 17:44:26
|
problem # 1: i just compiled and installed oprofile-0.5.1 on redhat 7.3. when i try to start the daemon, i get the following error: modprobe: Can't locate module oprofile i was able to insmod the module and started ok. i noticed that the new module was installed as /lib/modules/2.4.18-3custom/oprofile/oprofile.o. for grins, i created a link under /lib/modules/2.4.18-3 to same but no dice. how should i set it up so that it finds the module?... /etc/modules.conf alias? problem # 2: i'm running win4lin which provides a patched kernel. it's a compressed, x86 image file. when i passed it as my --vmlinux argument, it told me that it wasn't a valid vmlinux file. i understand that but given that i only have the x86 image, what can i do? is there a way to extract the uncompressed kernel from the x86 image file? thanks. -- Regards, Scott Dudley SPAMMERSNEEDNTBOTHER |
From: John L. <le...@mo...> - 2003-03-11 20:31:17
|
On Tue, Mar 11, 2003 at 10:44:15AM -0700, Scott Dudley wrote: > i just compiled and installed oprofile-0.5.1 on redhat 7.3. when i try > to start the daemon, i get the following error: OK I added this to the FAQ finally. > i'm running win4lin which provides a patched kernel. it's a compressed, > x86 image file. when i passed it as my --vmlinux argument, it told me > that it wasn't a valid vmlinux file. i understand that but given that i > only have the x86 image, what can i do? is there a way to extract the > uncompressed kernel from the x86 image file? http://oprofile.sf.net/faq/ john |
From: Vladimir G. I. <vla...@ac...> - 2003-03-11 21:17:47
|
I have had zero (0.0000000000%) success getting OProfile to build and run on Red Hat 8.0. I have read the FAQ. I have followed the instructions in the FAQ. I have read the README in the CVS distribution. I have followed the instructions in the README. My build and install have been successful, but I ALWAYS get exactly the same error: op_start --vmlinux=/boot/vmlinux-2.4.18-26.8.0smp --ctr0-event=CPU_CLK_UNHALTED --ctr0-count=300000 modprobe: Can't locate module oprofile Couldn't load oprofile.o module Which is not a surprise: no file called oprofile.o is created by the build. What does it take to get OProfile to work with a stock Red Hat 8.0 (2.4.18-26.8.0smp) distribution? Just so there is no confusion, a shell script would be appreciated. Here's the start of it (corrections gratefully accepted): #!/bin/sh cd /usr/local/src/oprofile autogen.sh ./configure --with-linux=/usr/src/linux-2.4.18-26.8.0 make install What next? Thanks. --- Vladimir ------------------------------------------------------------------------ Vladimir G. Ivanovic http://leonora.org/~vladimir 2770 Cowper St. vla...@ac... Palo Alto, CA 94306-2447 +1 650 678 8014 |
From: John L. <le...@mo...> - 2003-03-11 21:59:14
|
On Tue, Mar 11, 2003 at 01:17:42PM -0800, Vladimir G. Ivanovic wrote: > I have had zero (0.0000000000%) success getting OProfile to build and > run on Red Hat 8.0. Haven't we already explained this ? Use Red Hat's OProfile, not this distribution: it won't work as you have discovered. The Red Hat oprofile RPM comes with the distribution ... john |
From: William C. <wc...@nc...> - 2003-03-11 22:35:26
|
Looks like it is time to put an entry in the FAQ page: Why doesn't OProfile work with Red Hat 8.0? The Red Hat Linux 8.0 kernel only supports the OProfile shipped with Red Hat Linux 8.0. The Red Hat Linux 8.0 kernel does not export the sys_call_table symbol required by the OProfile modules built from source code. Either use the OProfile supplied with Red Hat Linux 8.0 or use a Linux kernel that exports sys_call_table or provides the new OProfile kernel ABI. -Will John Levon wrote: > On Tue, Mar 11, 2003 at 01:17:42PM -0800, Vladimir G. Ivanovic wrote: > > >>I have had zero (0.0000000000%) success getting OProfile to build and >>run on Red Hat 8.0. > > > Haven't we already explained this ? Use Red Hat's OProfile, not this > distribution: it won't work as you have discovered. > > The Red Hat oprofile RPM comes with the distribution ... > > john > > > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > oprofile-list mailing list > opr...@li... > https://lists.sourceforge.net/lists/listinfo/oprofile-list > |
From: John L. <le...@mo...> - 2003-03-11 22:45:32
|
On Tue, Mar 11, 2003 at 05:33:54PM -0500, William Cohen wrote: > Looks like it is time to put an entry in the FAQ page: > > Why doesn't OProfile work with Red Hat 8.0? I've just added a mention of 7.3, I guess I should add it for 8.0 too john |
From: William C. <wc...@nc...> - 2003-03-11 20:33:04
|
Scott Dudley wrote: > > problem # 1: > > i just compiled and installed oprofile-0.5.1 on redhat 7.3. when i try > to start the daemon, i get the following error: The sources Red Hat distributes in /usr/src/linux-2.4 have the Makefile add the "custom". This is to make sure that modules from the distro do not get overwritten. > modprobe: Can't locate module oprofile > > i was able to insmod the module and started ok. i noticed that the new > module was installed as /lib/modules/2.4.18-3custom/oprofile/oprofile.o. > for grins, i created a link under /lib/modules/2.4.18-3 to same but no > dice. how should i set it up so that it finds the module?... > /etc/modules.conf alias? I don't think mixing modules from different directories is going to work. There is some version checking of symbol names. The symbol names can be different depending on the .config. > problem # 2: > > i'm running win4lin which provides a patched kernel. it's a compressed, > x86 image file. when i passed it as my --vmlinux argument, it told me > that it wasn't a valid vmlinux file. i understand that but given that i > only have the x86 image, what can i do? is there a way to extract the > uncompressed kernel from the x86 image file? Is the win4lin kernel the same or different kernel than the one used for "problem #1?" I am not familar with win4lin. Is it using the stock redhat 7.3 kernel modules? Currently, OProfile doesn't know about compressed kernel or modules. It assumes everything is uncompress. Thus when opcontrol tries to extract the start and end addresses from a compressed kernel it fails. There should be some way to realize the file isn't uncompress, uncompress the file, and extract the information. -Will |
From: John L. <le...@mo...> - 2003-03-11 21:01:50
|
On Tue, Mar 11, 2003 at 03:28:04PM -0500, William Cohen wrote: > assumes everything is uncompress. Thus when opcontrol tries to extract > the start and end addresses from a compressed kernel it fails. There > should be some way to realize the file isn't uncompress, uncompress the > file, and extract the information. The vmlinux is stripped before being packaged into vmlinuz, so it's not possible/useful john p.s. Scott, there's some stupid "Won't accept emails from your location" thing that means I can't email you ... how about fixing it ? |