From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] floating-point error
Date: Thu, 17 Apr 2003 20:27:24 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705544@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705538@msgid-missing>
Great, thanks Bjorn.
Jesse
On Thu, Apr 17, 2003 at 02:06:42PM -0600, Bjorn Helgaas wrote:
> On Thursday 17 April 2003 1:52 pm, Jesse Barnes wrote:
> > It would be helpful to apply the patch that Martin Hicks sent out
> > awhile ago which will print the isr as well as the IP. You can then
> > decode the isr to figure out exactly what's causing the fault in your
> > app.
>
> I couldn't find this in the archives, but I got it out of David's
> 2.5 tree, and applied it for 2.4 as well. Here it is if you
> want to try it:
>
> # This is a BitKeeper generated patch for the following project:
> # Project Name: Linux kernel tree
> # This patch format is intended for GNU patch command version 2.5 or higher.
> # This patch includes the following deltas:
> # ChangeSet 1.889.308.20 -> 1.889.308.21
> # arch/ia64/kernel/traps.c 1.26 -> 1.26.1.1
> #
> # The following is the BitKeeper ChangeSet Log
> # --------------------------------------------
> # 03/03/18 mort@wildopensource.com 1.889.308.21
> # [PATCH] ia64: print ISR for FPSWA faults
> #
> # Here is a simple patch to also print isr during the handling of a
> # floating point assist fault.
> # --------------------------------------------
> #
> diff -Nru a/arch/ia64/kernel/traps.c b/arch/ia64/kernel/traps.c
> --- a/arch/ia64/kernel/traps.c Thu Apr 17 13:41:11 2003
> +++ b/arch/ia64/kernel/traps.c Thu Apr 17 13:41:11 2003
> @@ -336,8 +336,8 @@
> fpu_swa_count = 0;
> if ((++fpu_swa_count < 5) && !(current->thread.flags & IA64_THREAD_FPEMU_NOPRINT)) {
> last_time = jiffies;
> - printk(KERN_WARNING "%s(%d): floating-point assist fault at ip %016lx\n",
> - current->comm, current->pid, regs->cr_iip + ia64_psr(regs)->ri);
> + printk(KERN_WARNING "%s(%d): floating-point assist fault at ip %016lx, isr %016lx\n",
> + current->comm, current->pid, regs->cr_iip + ia64_psr(regs)->ri, isr);
> }
>
> exception = fp_emulate(fp_fault, bundle, ®s->cr_ipsr, ®s->ar_fpsr, &isr, ®s->pr,
next prev parent reply other threads:[~2003-04-17 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 19:21 [Linux-ia64] floating-point error Bruno Cornec
2003-04-17 19:52 ` Jesse Barnes
2003-04-17 20:06 ` Bjorn Helgaas
2003-04-17 20:25 ` David Mosberger
2003-04-17 20:27 ` Jesse Barnes [this message]
2003-04-17 20:40 ` Luck, Tony
2003-04-17 20:40 ` Bruno Cornec
2003-04-17 21:12 ` Chen, Kenneth W
2003-04-17 23:57 ` martin sepulveda
2003-04-17 23:59 ` martin sepulveda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590723705544@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox