From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Description of problem:
If the oprofile daemon runs for too long it "freezes" the system. This
has happened on two different machines. I configure oprofile by typing
opcontrol --vmlinux=/boot/vmlinux-`uname -r`
I then start the profiling by typing
It runs for quite a while, but inevitably it freezes the system after
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. opcontrol --vmlinux=/boot/vmlinux-`uname -r`
2. opcontrol --start
3. Wait several hours
OProfile is very closely tied to the hardware and the kernel. Please
include information about which kernel is being used (uname -a), what
processor (cat /proc/cpuinfo), and what motherboard are being used.
Are the machines the same or are there difference between them.
Are the machines idles when this is going on? Or are you actively
working on something on the machines when they freeze.
Created attachment 100738 [details]
The output of 'cat /proc/cpuinfo'
Here is the output of uname -a:
Linux carla.library.uiuc.edu 2.4.21-15.ELsmp #1 SMP Thu Apr 22
00:18:24 EDT 2004 i686 i686 i386 GNU/Linux
The system is a stock Dell PowerEdge 2500. I will try to find the
There were some changes made in the Kernel OProfile support in the
RHEL3 U3. I suspect that these changes fix the problem that you were
having. I have been able to run OProfile on a PIII Dell precision 420
for several days at a time without a problem.
Could you verify that the new kernel resolves the issue?