Bug 211652 - crash generates floating point assist faults on ia64
crash generates floating point assist faults on ia64
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: crash (Show other bugs)
ia64 Linux
medium Severity low
: ---
: ---
Assigned To: Dave Anderson
Depends On:
  Show dependency treegraph
Reported: 2006-10-20 12:52 EDT by Bryn M. Reeves
Modified: 2010-10-22 02:35 EDT (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2007-0188
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-01 18:45:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
backtrace from the location triggering the fp assist fault (7.36 KB, text/plain)
2006-10-20 12:52 EDT, Bryn M. Reeves
no flags Details
prctl(PR_SET_FPEMU, 1, 0, 0, 0); (553 bytes, patch)
2006-10-20 14:13 EDT, Dave Anderson
no flags Details | Diff

  None (edit)
Description Bryn M. Reeves 2006-10-20 12:52:47 EDT
The gdb module in crash attempts to manipulate floating point values via ldexp
when printing backtraces. If the values in the fp registers contain
denormals/NANs, the kernel logs a floating point software assist fault.

The messages are low in volume and the concern is primarily cosmetic.

Steps to reproduce:

# rpm -ivh kernel-2.6.9-42.EL.ia64.rpm
# crash /usr/lib/debug/lib/modules/2.6.9-42.EL/vmlinux

crash> foreach bt

# dmesg|grep "assist fault"
kernel: crash(12028): floating-point assist fault at ip 20000000000d4382, isr

The ip is always inside ldexp, being called from the gdb value_print function
(see attached backtrace)
Comment 1 Bryn M. Reeves 2006-10-20 12:52:58 EDT
Created attachment 139001 [details]
backtrace from the location triggering the fp assist fault
Comment 2 Dave Anderson 2006-10-20 13:47:26 EDT
Interesting, although I can't reproduce it, at least with 2.4.21-47.EL.

It looks like the messages can be turned off on a per-task basis
with a prctl PR_SET_FPEMU in order to set the IA64_THREAD_FPEMU_NOPRINT
bit in its current->thread.flags.

Comment 3 Dave Anderson 2006-10-20 14:13:39 EDT
Created attachment 139012 [details]
prctl(PR_SET_FPEMU, 1, 0, 0, 0);


If you get the chance, can you apply this patch to the ia64.c file
in the crash utility sources, rebuild, and see if it clears up the
log messages?

The patch is against the 4.0-3.7 version of crash, but will probably
apply to whatever you're using.  But the easiest thing to do would
be to go to http://people.redhat.com/anderson and download the
crash-4.0-3.7.tar.gz file.  Then:

# tar xzf crash-4.0-3.7.tar.gz
# cd crash-4.0-3.7
# patch -p0 < ia64_prctl.patch
# make
# ./crash

and test it out.
Comment 4 Dave Anderson 2006-10-20 15:27:14 EDT
Or, alternatively, this should accomplish the same thing with
the crash utility unmodified:

 # prctl --fpemu=silent crash 
Comment 6 Bryn M. Reeves 2006-10-23 07:07:52 EDT
Have tested both the prctl workaround and the patch (applied to the U4 crash
sources - went in fine with a bit of offset) - both worked like a charm, thanks!
Comment 7 Dave Anderson 2006-10-24 08:35:13 EDT
This should go into the RHEL4-5 crash utility errata.
Comment 8 RHEL Product and Program Management 2006-10-24 08:43:32 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 9 Dave Anderson 2006-11-03 10:26:26 EST
I am currently filing the RHEL4-U5 crash utility errata, and
for inclusion this Bugzilla needs:

 rhel-4-5 +
 devel.ack + 
 qa_ack +

Comment 11 Dave Anderson 2006-11-03 14:40:31 EST
crash version 4.0-3.9 checked into RHEL4 CVS.

(still requires devel_ack+, qa_ack+ and rhel-4.5+)
Comment 16 Red Hat Bugzilla 2007-05-01 18:45:21 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.