Red Hat Bugzilla – Bug 152103
RHEL3 U5: rhgb-client shows illegal instruction and fails.
Last modified: 2007-11-30 17:07:06 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; YPC 3.0.1; .NET CLR 1.1.4322)
Description of problem:
rhgb-client shows illegal instruction and fails. The fix for 2.6 is being discussed in lkml. We will backport to RHEL3 as soon as it's accepted upstream and attach it to this bugzilla.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run "rhgb-client".
2. Returns illegal instructions and fails.
Actual Results: rhgb-client shows illegal instructions and fails.
Expected Results: rhgb-client should run scuccessfully.
This problem can be exhibited by different applications. We have started the
discussions on LKML to resolve this issue.
Created attachment 112442 [details]
Fixing cache coherency issue on Montecito
This patch fixes cache coherency issue on Montecito which causes illegal
instructions when running rhgb-client etc.
The fix has been accepted upstream in 2.6 base kernel. This patch is back
ported from upstream fix.
Reassigning to Geoff. Jason's busy with RHEL4.
This might be related to bug 165769 (according to Geoff).
Geoff, does this really need to be Intel-confidential?
The fix is in base kernel already. This is NOT Intel confidential.
To verify if it's related to bug 165769, please apply this patch on your
kernel and try it.
Okay, thanks. Could you please uncheck the Intel Confidential Group
box below then? As soon as you do this, I'll then uncheck the various
Red Hat Confidential groups so that the bug report will become public.
Thanks in advance.
Regarding comment #7, it looks like bug 165769 was a different problem.
A fix for this problem has just been committed to the RHEL3 U7
patch pool this evening (in kernel version 2.4.21-37.10.EL).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.