[Bug kprobes/2091] system crash when running "./systemtap.stress/current.stp" on power

["ananth at in dot ibm dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From ananth at in dot ibm dot com  2006-08-04 05:01 -------
I tried to recreate this problem on a POWER4 LPAR:

[root@llm16 systemtap.stress]# cat /proc/cpuinfo
processor       : 0
cpu             : POWER4+ (gq)
clock           : 1200.791720MHz
revision        : 18.3 (pvr 0038 1203)

processor       : 1
cpu             : POWER4+ (gq)
clock           : 1200.791720MHz
revision        : 18.3 (pvr 0038 1203)

timebase        : 150098965
platform        : pSeries
machine         : CHRP IBM,7028-6C4

The test ran just fine, for two iterations atleast:

[root@llm16 systemtap.stress]# stap -g current.stp
systemtap starting probe
systemtap ending probe
count = 5889610
sum = 40002649
min = 3
max = 11
avg = 6
systemtap test success
systemtap test success
[root@llm16 systemtap.stress]# stap -g current.stp
systemtap starting probe
systemtap ending probe
count = 16514488
sum = 112075474
min = 3
max = 15
avg = 6
systemtap test success
systemtap test success
WARNING: Number of errors: 0, skipped probes: 440
[root@llm16 systemtap.stress]#

This machine is running RHEL (U3)
[root@llm16 systemtap.stress]# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 4 (Nahant Update 3)

But the kernel running at the time is upstream 2.6.18-rc3 (compiled with
pseries_defconfig):

[root@llm16 systemtap.stress]# uname -a
Linux llm16.in.ibm.com 2.6.18-rc3 #4 SMP Wed Aug 2 17:50:14 IST 2006 ppc64 ppc64
ppc64 GNU/Linux

I'll try to increase the test run duration to see if the problem can be recreated. 

Mike, Jian Gui, was the problem with just the RHEL4-Ux kernel? Can you please
try the same test with the upstream kernel?

Ananth

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2091

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.