From: Paul Mackerras <paulus@samba.org>
To: "McMullan, Jason" <jason.mcmullan@timesys.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: FPSCR corruption
Date: Thu, 17 Jun 2004 08:15:12 +1000 [thread overview]
Message-ID: <16592.50800.578068.287308@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <1087409391.14878.92.camel@veena.timesys>
> Oddity. I'm seeing SIGFPEs arrive in the wrong process.
>
> I'm seeing this in my 2.4.x kernels, on 8260 and 750 cpus (and anything
> else that has an FPU).
Hmmm, it doesn't fail for me, e.g. on a G4 cube (7400 cpu) running
2.4.23, or on a dual G5 running 2.6.7-rc2 ppc64.
We used to have a bug that would cause this but it got fixed quite a
while ago now. What kernel version are you using?
Paul.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-06-16 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 18:09 FPSCR corruption McMullan, Jason
2004-06-16 22:15 ` Paul Mackerras [this message]
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=16592.50800.578068.287308@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=jason.mcmullan@timesys.com \
--cc=linuxppc-embedded@lists.linuxppc.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