Skip to contentSkip to conversation

oprofile broken on 2.6.19

DISCUSSION Gert Vervoort 3 participants 7 messages Jan 9, 2007 – Jan 11, 2007

lore
Share & tools
lore
#0 lore raw

When I try to use oprofile on 2.6.19, it does not seem to work:

[gert@apollo tmp]$ sudo opcontrol --no-vmlinux
[gert@apollo tmp]$ sudo opcontrol --start
/usr/bin/opcontrol: line 911: /dev/oprofile/0/enabled: No such file or directory/usr/bin/opcontrol: line 911: /dev/oprofile/0/event: No such file or directory /usr/bin/opcontrol: line 911: /dev/oprofile/0/count: No such file or directory
/usr/bin/opcontrol: line 911: /dev/oprofile/0/kernel: No such file or directory
/usr/bin/opcontrol: line 911: /dev/oprofile/0/user: No such file or directory
/usr/bin/opcontrol: line 911: /dev/oprofile/0/unit_mask: No such file or directory
Using 2.6+ OProfile kernel interface.
Using log file /var/lib/oprofile/oprofiled.log
Daemon started.
Profiler running.
[gert@apollo tmp]$ ls /dev/oprofile/

1  backtrace_depth  buffer_watershed  dump          stats
2  buffer           cpu_buffer_size   enable
3  buffer_size      cpu_type          pointer_size

[gert@apollo tmp]$ cat /var/lib/oprofile/oprofiled.log
oprofiled started Tue Jan 9 21:41:02 2007
kernel pointer size: 8
[gert@apollo tmp]$ uname -a
Linux apollo 2.6.19 #1 PREEMPT Thu Nov 30 18:52:13 CET 2006 x86_64 x86_64 x86_64 GNU/Linux [gert@apollo tmp]$

Gert

#6 lore raw
In reply to Gert Vervoort
Quoted 8 lines · Gert Vervoort

When I try to use oprofile on 2.6.19, it does not seem to work:

[gert@apollo tmp]$ sudo opcontrol --no-vmlinux
[gert@apollo tmp]$ sudo opcontrol --start /usr/bin/opcontrol: line 911: /dev/oprofile/0/enabled: No such file or directory/usr/bin/opcontrol: line 911: /dev/oprofile/0/event: No such file or directory

oh.. and next time please first try google ;)
http://www.google.ch/search?q=%2Fdev%2Foprofile%2F0%2Fevent

tom

#3 lore raw
Quoted 10 lines · Gert Vervoort
Quoted 5 lines · Tomas Carnecky
Quoted 2 lines · Gert Vervoort

When I try to use oprofile on 2.6.19, it does not seem to work:

http://lkml.org/lkml/2006/11/22/172

Disabling the nmi watchdog, as suggested in:
http://marc.theaimsgroup.com/?l=oprofile-list&m=116422889324043&w=2,
also makes oprofile work again.

Oh.. that seem to be much easier then compiling a patched oprofile :) However, I can't find any NMI option (grep NMI .config), and CONFIG_WATCHDOG is disabled here.

tom

#4 lore raw
Quoted 7 lines · Tomas Carnecky
Quoted 6 lines · Gert Vervoort
Quoted 4 lines · Tomas Carnecky
Quoted 1 line · Gert Vervoort

When I try to use oprofile on 2.6.19, it does not seem to work:

http://lkml.org/lkml/2006/11/22/172

Quoted 7 lines
Quoted 3 lines

Disabling the nmi watchdog, as suggested in:
http://marc.theaimsgroup.com/?l=oprofile-list&m=116422889324043&w=2,
also makes oprofile work again.

Oh.. that seem to be much easier then compiling a patched oprofile :) However, I can't find any NMI option (grep NMI .config), and CONFIG_WATCHDOG is disabled here.

Sure, but did you tried to boot with 'nmi_watchdog=0' appended in your boot params ?

Eric

#5 lore raw
Quoted 9 lines · Eric Dumazet
Quoted 8 lines · Tomas Carnecky
Quoted 7 lines · Gert Vervoort
Quoted 3 lines · Tomas Carnecky
Quoted 1 line · Gert Vervoort

When I try to use oprofile on 2.6.19, it does not seem to work:

http://lkml.org/lkml/2006/11/22/172

Disabling the nmi watchdog, as suggested in:
http://marc.theaimsgroup.com/?l=oprofile-list&m=116422889324043&w=2,
also makes oprofile work again.

Quoted 6 lines
Quoted 3 lines

Oh.. that seem to be much easier then compiling a patched oprofile :) However, I can't find any NMI option (grep NMI .config), and CONFIG_WATCHDOG is disabled here.

Sure, but did you tried to boot with 'nmi_watchdog=0' appended in your boot params ?

No, I assumed since I don't have any watchdog, I wouldn't have the NMI thing either... these silly assumptions.

tom