From: Troy Benjegerdes <hozer@drgw.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: calling giveup_altivec on machine with no altivec!?
Date: Thu, 15 Feb 2001 16:06:58 -0600 [thread overview]
Message-ID: <20010215160658.P26702@altus.drgw.net> (raw)
My Motorola MTX just crashed after the following code in _swithc_to
executed:
if ((prev->thread.regs && (prev->thread.regs->msr & MSR_VEC)))
giveup_altivec(prev);
Somehow prev->thread.regs->msr & MSR_VEC turned out true. I'm suspecting
something got overwritten somewhere..
This is an SMP machine so I'm wondering if there wasn't a race condition
on something with task structs..
--------------------------------------------------------------------------
Troy Benjegerdes 'da hozer' hozer@drgw.net
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-02-15 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 22:06 Troy Benjegerdes [this message]
2001-02-15 22:20 ` calling giveup_altivec on machine with no altivec!? Frank Rowand
2001-02-15 22:33 ` Troy Benjegerdes
2001-02-15 22:47 ` Frank Rowand
2001-02-15 22:39 ` program exception emulates mfspr PVR Frank Rowand
2001-02-15 22:52 ` Dan Malek
2001-02-15 23:41 ` Mark Hatle
2001-02-15 22:57 ` calling giveup_altivec on machine with no altivec!? Dan Malek
2001-02-18 2:41 ` Troy Benjegerdes
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=20010215160658.P26702@altus.drgw.net \
--to=hozer@drgw.net \
--cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.