From: Heckel, D. <dh...@so...> - 2012-11-06 19:50:03
|
I am running into a system freeze after entering oprofile --start. I do not see any kernel oops message on the console. This is under Fedora Core 9 with oprofile built as a module. When I increased the count, it took slightly more time before the system locked up. cat ~/.oprofile/daemonrc SESSION_DIR=/var/lib/oprofile CHOSEN_EVENTS_0=CPU_CLK_UNHALTED:10000000:0:1:1 NR_CHOSEN=1 SEPARATE_LIB=0 SEPARATE_KERNEL=0 SEPARATE_THREAD=0 SEPARATE_CPU=0 VMLINUX=/usr/src/redhat/BUILD/kernel-2.6.27/linux-2.6.27.i686/vmlinux IMAGE_FILTER= CPU_BUF_SIZE=0 CALLGRAPH=0 KERNEL_RANGE=c0401000,c064afc8 XENIMAGE=none uname -a Linux physim11 2.6.27.25-78.2.56.local.fc9.i686 #1 SMP Mon Nov 5 14:56:10 PST 2012 i686 i686 i386 GNU/Linux cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU W3550 @ 3.07GHz stepping : 5 cpu MHz : 3066.773 cache size : 8192 KB physical id : 1 siblings : 8 core id : 0 cpu cores : 4 apicid : 16 initial apicid : 16 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 sse4_2 popcnt lahf_lm ida bogomips : 6133.54 clflush size : 64 power management: ... Anybody have any suggestions? |
From: Maynard J. <may...@us...> - 2012-11-08 01:24:22
|
On 11/06/2012 01:34 PM, Heckel, Dan wrote: > I am running into a system freeze after entering oprofile --start. I do not see any kernel oops message on the console. This is under Fedora Core 9 with oprofile built as a module. When I increased the count, it took slightly more time before the system locked up. Dan, a system freeze is something we'd need kernel expertise to help with, so I'm pulling Robert into this conversation. *Robert*, do you have any knowledge of system hangs with the platform Dan's on? -Maynard > > > > cat ~/.oprofile/daemonrc > > SESSION_DIR=/var/lib/oprofile > > CHOSEN_EVENTS_0=CPU_CLK_UNHALTED:10000000:0:1:1 > > NR_CHOSEN=1 > > SEPARATE_LIB=0 > > SEPARATE_KERNEL=0 > > SEPARATE_THREAD=0 > > SEPARATE_CPU=0 > > VMLINUX=/usr/src/redhat/BUILD/kernel-2.6.27/linux-2.6.27.i686/vmlinux > > IMAGE_FILTER= > > CPU_BUF_SIZE=0 > > CALLGRAPH=0 > > KERNEL_RANGE=c0401000,c064afc8 > > XENIMAGE=none > > > > uname -a > > Linux physim11 2.6.27.25-78.2.56.local.fc9.i686 #1 SMP Mon Nov 5 14:56:10 PST 2012 i686 i686 i386 GNU/Linux > > > > cat /proc/cpuinfo > > processor : 0 > > vendor_id : GenuineIntel > > cpu family : 6 > > model : 26 > > model name : Intel(R) Xeon(R) CPU W3550 @ 3.07GHz > > stepping : 5 > > cpu MHz : 3066.773 > > cache size : 8192 KB > > physical id : 1 > > siblings : 8 > > core id : 0 > > cpu cores : 4 > > apicid : 16 > > initial apicid : 16 > > fdiv_bug : no > > hlt_bug : no > > f00f_bug : no > > coma_bug : no > > fpu : yes > > fpu_exception : yes > > cpuid level : 11 > > wp : yes > > flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 sse4_2 popcnt lahf_lm ida > > bogomips : 6133.54 > > clflush size : 64 > > power management: > > … > > > > Anybody have any suggestions? > > > > > > ------------------------------------------------------------------------------ > LogMeIn Central: Instant, anywhere, Remote PC access and management. > Stay in control, update software, and manage PCs from one command center > Diagnose problems and improve visibility into emerging IT issues > Automate, monitor and manage. Do more in less time with Central > http://p.sf.net/sfu/logmein12331_d2d > > > > _______________________________________________ > oprofile-list mailing list > opr...@li... > https://lists.sourceforge.net/lists/listinfo/oprofile-list |
From: Robert R. <rr...@ke...> - 2012-11-20 11:47:11
|
On 07.11.12 19:24:10, Maynard Johnson wrote: > *Robert*, do you have any knowledge of system hangs with the > platform Dan's on? Kernel 2.6.27 of Fedora core 9 seems pretty old. Is the cpu properly detected (dev/oprofile/cpu_type should be i386/core_i7)? What shows dmesg after loading the oprofile module? Is there something like: oprofile: using NMI timer interrupt This would indicate the cpu is properly detected. Otherwise software counters are used which might not work properly on that kernel. Then, the following message occurs: oprofile: using timer interrupt -Robert |
From: Heckel, D. <dh...@so...> - 2012-11-20 20:37:58
|
-----Original Message----- From: Robert Richter [mailto:rri...@gm...] On Behalf Of Robert Richter Sent: Tuesday, November 20, 2012 3:47 AM To: Maynard Johnson Cc: Heckel, Dan; opr...@li... Subject: Re: System freezes after opcontrol --start On 07.11.12 19:24:10, Maynard Johnson wrote: > *Robert*, do you have any knowledge of system hangs with the platform > Dan's on? Kernel 2.6.27 of Fedora core 9 seems pretty old. Is the cpu properly detected (dev/oprofile/cpu_type should be i386/core_i7)? What shows dmesg after loading the oprofile module? Is there something like: oprofile: using NMI timer interrupt This would indicate the cpu is properly detected. Otherwise software counters are used which might not work properly on that kernel. Then, the following message occurs: oprofile: using timer interrupt -Robert ---------------------------- Hi Robert, When I insert the module without any parameters I this in dmesg: oprofile: using NMI interrupt. /dev/oprofile does not exist. I think it only exists after opcontrol --start which I cannot do because it locks up the system. If I set the module parameter timer=1, I can do timer based profiling without the system lockup. Once I start profiling in timer mode, I have a /dev/oprofile/cpu_type, which just reads "timer". Thanks, Dan |
From: Robert R. <rr...@ke...> - 2012-11-22 11:51:04
|
On 20.11.12 20:22:37, Heckel, Dan wrote: > When I insert the module without any parameters I this in dmesg: > oprofile: using NMI interrupt. So a cpu was detected. > /dev/oprofile does not exist. I think it only exists after > opcontrol --start which I cannot do because it locks up the system. opcontrol --init should work too to mount it. Or, you mount it manually: mount -t oprofilefs nodev /dev/oprofile Would be interesting to see cpu_type for this. Which kernel are you using exactly? Mind upgrading your kernel? -Robert |
From: Heckel, D. <dh...@so...> - 2012-11-26 19:33:44
|
-----Original Message----- From: Robert Richter [mailto:rri...@gm...] On Behalf Of Robert Richter Sent: Thursday, November 22, 2012 3:51 AM To: Heckel, Dan Cc: Maynard Johnson; opr...@li... Subject: Re: System freezes after opcontrol --start On 20.11.12 20:22:37, Heckel, Dan wrote: > When I insert the module without any parameters I this in dmesg: > oprofile: using NMI interrupt. So a cpu was detected. > /dev/oprofile does not exist. I think it only exists after opcontrol > --start which I cannot do because it locks up the system. opcontrol --init should work too to mount it. Or, you mount it manually: mount -t oprofilefs nodev /dev/oprofile Would be interesting to see cpu_type for this. Which kernel are you using exactly? Mind upgrading your kernel? -Robert ------------------------------- Hi Robert, Looks like cpu_type is i386/core_2. I am using a 2.6.27 kernel. I have tried upgrading the kernel... I managed to get a 2.6.29 for FC10 to work but that didn't help. I ran into all sorts of trouble trying to build a 2.6.31 from FC11. For now I am getting good results using timer mode so I will probably just stick with what I have. Thanks for the help. --Dan |