Bug 711387 - ppc-dabr-race -m64: watchpoint missed and hit in wrong place during continue, on a specific ppc box
Summary: ppc-dabr-race -m64: watchpoint missed and hit in wrong place during continue,...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.6
Hardware: ppc64
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Steve Best
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On: 444076
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-07 11:02 UTC by Petr Muller
Modified: 2016-09-20 02:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-04 20:37:36 UTC
Target Upstream Version:

Attachments (Terms of Use)
testcase (8.44 KB, text/plain)
2011-06-07 11:02 UTC, Petr Muller 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Comment 1 Jan Kratochvil 2011-06-10 22:37:02 UTC 
wget -O ppc-dabr-race.c 'http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/tests/ptrace-tests/tests/ppc-dabr-race.c?cvsroot=systemtap'; gcc -o ppc-dabr-race ppc-dabr-race.c -Wall -ggdb2 -m64 -D_GNU_SOURCE -pthread; ./ppc-dabr-race; echo $?
FAIL = 1
PASS = 0

FAIL kernel-2.6.18-238.el5.ppc64 RHEL-5.6 ibm-js20-04.lab.bos.redhat.com
        processor : 1 --- 2 processors
        cpu   : PPC970FX, altivec supported
        clock   : 2194.624509MHz
        revision  : 3.1 (pvr 003c 0301)
        timebase  : 14318000
        platform  : pSeries
        machine   : CHRP IBM,8842-4TX

PASS kernel-2.6.18-238.el5.ppc64 RHEL-5.6 ppcp-5s-m1.ss.eng.bos.redhat.com
        processor : 3 --- 4 processors
        cpu   : POWER5 (gr)
        clock   : 1654.344000MHz
        revision  : 2.3 (pvr 003a 0203)
        timebase  : 207001000
        platform  : pSeries
        machine   : CHRP IBM,9123-710

I have seen FAIL on the first machine even with -m32 but that is unreliable.

It was filed before as Bug 437970 -> Bug 444076.
Is this a kernel regression or hardware problem?
Comment 2 RHEL Program Management 2012-01-09 14:28:19 UTC 
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.8 and Red Hat does not plan to fix this issue the currently developed update.

Contact your manager or support representative in case you need to escalate this bug.
Comment 4 RHEL Program Management 2012-10-30 05:47:19 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 5 Steve Best 2013-12-04 20:37:36 UTC 
This isn't a high priority bug and this won't be fixed for rhel 5.11 or in any rhel 5.x. closing
Note You need to log in before you can comment on or make changes to this bug.