From: Liu bo <bo...@ho...> - 2012-06-19 09:47:54
|
Hi folks, I always got below error using oprofile 0.9.4 with kernel version3.3. =========================== mkdir -p /var/lib/oprofile/samples opcontrol --init oprofiled -e '' --no-vmlinux --session-dir=/var/lib/oprofile --image=/usr/bin/whetstone & opcontrol --start whetstone opcontrol --dump root:/> opreport -lw opreport error: Invalid sample file, bad magic number: /var/lib/oprofile/samples/current/{root}/usr/bin/whetstone/{dep}/{root}/usr/bin/whetstone/TIMER.0.0.all.all.all root:/> ============================ Any ideas? Thank you! -- Best regards -Bob Liu |
From: Maynard J. <may...@us...> - 2012-06-19 14:10:42
|
On 06/19/2012 04:47 AM, Liu bo wrote: > Hi folks, > > I always got below error using oprofile 0.9.4 with kernel version3.3. > =========================== > mkdir -p /var/lib/oprofile/samples > opcontrol --init > oprofiled -e '' --no-vmlinux --session-dir=/var/lib/oprofile --image=/usr/bin/whetstone & > opcontrol --start > whetstone > opcontrol --dump > > root:/> opreport -lw > opreport error: Invalid sample file, bad magic number: /var/lib/oprofile/samples/current/{root}/usr/bin/whetstone/{dep}/{root}/usr/bin/whetstone/TIMER.0.0.all.all.all This usually implies that opreport is finding samples collected from two different versions of oprofile. I suggest you wipe everything clean ('rm /root/.oprofile/daemonrc' and 'opcontrol --reset') and try again. You usually want to do 'opcontrol --reset' prior to starting any profiling session, else you'll be appending new profile data to previous profile data. By the way, I notice above that you're starting oprofiled manually. Don't do that unless there's a real good reason. The 'opcontrol --start' will automatically start oprofiled. -Maynard > root:/> > ============================ > > Any ideas? Thank you! > > -- > Best regards > -Bob Liu > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > > _______________________________________________ > oprofile-list mailing list > opr...@li... > https://lists.sourceforge.net/lists/listinfo/oprofile-list |
From: Liu bo <bo...@ho...> - 2012-06-20 03:44:09
|
> Date: Tue, 19 Jun 2012 09:09:49 -0500 > From: may...@us... > To: bo...@ho... > CC: opr...@li... > Subject: Re: [HELP]opreport error: Invalid sample file, bad magic number > > On 06/19/2012 04:47 AM, Liu bo wrote: > > Hi folks, > > > > I always got below error using oprofile 0.9.4 with kernel version3.3. > > =========================== > > mkdir -p /var/lib/oprofile/samples > > opcontrol --init > > oprofiled -e '' --no-vmlinux --session-dir=/var/lib/oprofile --image=/usr/bin/whetstone & > > opcontrol --start > > whetstone > > opcontrol --dump > > > > root:/> opreport -lw > > opreport error: Invalid sample file, bad magic number: /var/lib/oprofile/samples/current/{root}/usr/bin/whetstone/{dep}/{root}/usr/bin/whetstone/TIMER.0.0.all.all.all > This usually implies that opreport is finding samples collected from two different versions of oprofile. I suggest you wipe everything clean ('rm /root/.oprofile/daemonrc' and 'opcontrol --reset') and try again. You usually want to do 'opcontrol --reset' prior to starting any profiling session, else you'll be appending new profile data to previous profile data. By the way, I notice above that you're starting oprofiled manually. Don't do that unless there's a real good reason. The 'opcontrol --start' will automatically start oprofiled. I am using oprofile 0.9.4. I've try again following your suggetion like below: root:/> mkdir -p /var/lib/oprofile/samples root:/> root:/> opcontrol --reset root:/> opcontrol --init root:/> opcontrol --start --no-vmlinux --session-dir=/var/lib/oprofile --image=/ usr/bin/whetstone & [1] 387 opcontrol --start --no-vmlinux --session-dir=/var/lib/oprofile --image=/usr/bin/whetstone root:/> Using 2.6+ OProfile kernel interface. Using log file /var/lib/oprofile/samples/oprofiled.log root:/> whetstone Loops: 1000, Iterations: 1, Duration: 4 sec. C Converted Double Precision Whetstones: 25.0 MIPS root:/> opcontrol --dump root:/> root:/> opreport -lw opreport error: No sample file found: try running opcontrol --dump or specify a session containing sample files root:/> cat /var/lib/oprofile/samples/oprofiled.log oprofiled started Mon Jan 1 00:01:10 2007 kernel pointer size: 4 root:/> It seems this time no sample files were generated. But oprofile v0.9.1 works fine for me. Thank you! > > -Maynard > > root:/> > > ============================ > > > > Any ideas? Thank you! > -- Best regards -Bob Liu |
From: Maynard J. <may...@us...> - 2012-06-20 13:27:21
|
On 06/19/2012 10:44 PM, Liu bo wrote: > >> Date: Tue, 19 Jun 2012 09:09:49 -0500 >> From: may...@us... >> To: bo...@ho... >> CC: opr...@li... >> Subject: Re: [HELP]opreport error: Invalid sample file, bad magic number >> >> On 06/19/2012 04:47 AM, Liu bo wrote: >> > Hi folks, >> > >> > I always got below error using oprofile 0.9.4 with kernel version3.3. >> > =========================== >> > mkdir -p /var/lib/oprofile/samples >> > opcontrol --init >> > oprofiled -e '' --no-vmlinux --session-dir=/var/lib/oprofile --image=/usr/bin/whetstone & >> > opcontrol --start >> > whetstone >> > opcontrol --dump >> > >> > root:/> opreport -lw >> > opreport error: Invalid sample file, bad magic number: /var/lib/oprofile/samples/current/{root}/usr/bin/whetstone/{dep}/{root}/usr/bin/whetstone/TIMER.0.0.all! .all.all >> This usually implies that opreport is finding samples collected from two different versions of oprofile. I suggest you wipe everything clean ('rm /root/.oprofile/daemonrc' and 'opcontrol --reset') and try again. You usually want to do 'opcontrol --reset' prior to starting any profiling session, else you'll be appending new profile data to previous profile data. By the way, I notice above that you're starting oprofiled manually. Don't do that unless there's a real good reason. The 'opcontrol --start' will automatically start oprofiled. > > I am using oprofile 0.9.4. > I've try again following your suggetion like below: > root:/> mkdir -p /var/lib/oprofile/samples > root:/> > root:/> opcontrol --reset > root:/> opcontrol --init > > root:/> opcontrol --start --no-vmlinux --session-dir=/var/lib/oprofile --image=/ > usr/bin/whetstone & ^--- Don't put opcontrol in the background. There's no point, and it may just be causing your problem. > [1] 387 opcontrol --start --no-vmlinux --session-dir=/var/lib/oprofile --image=/usr/bin! /whetstone ^--- This looks suspicious. > root:/> Using 2.6+ OProfile kernel interface. > Using log file /var/lib/oprofile/samples/oprofiled.log > > root:/> whetstone > > Loops: 1000, Iterations: 1, Duration: 4 sec. > C Converted Double Precision Whetstones: 25.0 MIPS > root:/> opcontrol --dump > root:/> > root:/> opreport -lw > opreport error: No sample file found: try running opcontrol --dump > or specify a session containing sample files The first thing that you should do is remove the image specification you specified in the opcontrol start command, since there may be something about the specification that is wrong and causing oprofile to discard all samples. Remove that image spec using 'opcontrol --image=all'. The image spec is not needed for the profiling session. By default, oprofile will store samples for every process on the system. The image spec is useful if you have a long-running profiling session and want to save disk space. But oprofile sample data storage is pretty efficient and disk space gets cheaper every year, so it's just not a very useful option. When you generate a report, if you pass the name of the application of interest as the last argument to opreport, that will produce results just for that app versus the whole system; e.g., 'opreport -lw /usr/bin/whetstone'. -Maynard > > root:/> cat /var/lib/oprofile/samples/oprofiled.log > oprofiled started Mon Jan 1 00:01:10 2007 > kernel pointer size: 4 > root:/> > > It seems this time no sample files were generated. > > But oprofile v0.9.1 works fine for me. > Thank you! > >> >> -Maynard >> > root:/> >> > ============================ >> > >> > Any ideas? Thank you! >> > > -- > Best regards > -Bob Liu > > |