From: Jun Sun <jsun@mvista.com>
To: Joe deBlaquiere <jadb@redhat.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call
Date: Fri, 26 Jan 2001 13:02:57 -0800 [thread overview]
Message-ID: <20010126130257.I9325@mvista.com> (raw)
In-Reply-To: <3A71E037.6030300@redhat.com>; from jadb@redhat.com on Fri, Jan 26, 2001 at 02:38:15PM -0600
On Fri, Jan 26, 2001 at 02:38:15PM -0600, Joe deBlaquiere wrote:
>
> Jun Sun wrote:
>
> > On Thu, Jan 25, 2001 at 06:53:44PM -0600, Joe deBlaquiere wrote:
> >
> >> The end goal of this is to make pthreads work on the Vr4181...it's
> >> certainly an interesting task so far...
> >>
> >
> >
> > We have got pthreads working on Vr4181 for a couple of months already.
> > What version of kernel are you using? The toughest problem is not
> > MIPS_AUTOMIC_SET. It is a kernel s0 register corruption bug, which is
> > already fixed in the current CVS tree.
> >
>
> which current CVS tree, the linuxvr tree?
>
What do you think "CVS tree" is on an oss.sgi.com mailing list? :-0
> what is the s0 register corruption bug?
>
Check back with the mailing list archive. There was a thread about this.
Basically, the s0 register can be corrupted during a few syscalls.
pthread_create() uses one of the syscalls and thus fails even though the
new thread is actually created.
Jun
next prev parent reply other threads:[~2001-01-26 21:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 15:30 OOps - very obscure Florian Lohoff
2001-01-24 15:59 ` Florian Lohoff
2001-01-24 16:22 ` Florian Lohoff
2001-01-24 21:18 ` Keith Owens
2001-01-25 12:43 ` Florian Lohoff
2001-01-25 18:59 ` Jun Sun
2001-01-25 19:22 ` Florian Lohoff
2001-01-25 15:55 ` [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call Florian Lohoff
2001-01-25 15:55 ` Florian Lohoff
2001-01-25 16:34 ` Origin 200 crash nick
2001-01-25 18:28 ` [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call Joe deBlaquiere
2001-01-25 19:35 ` Joe deBlaquiere
2001-01-25 22:19 ` Ralf Baechle
2001-01-26 0:53 ` Joe deBlaquiere
2001-01-26 10:21 ` Maciej W. Rozycki
2001-01-26 15:41 ` Joe deBlaquiere
2001-01-26 21:16 ` Ralf Baechle
2001-01-27 7:20 ` Maciej W. Rozycki
2001-01-26 21:15 ` Ralf Baechle
2001-01-27 7:28 ` Maciej W. Rozycki
2001-01-27 19:42 ` Ralf Baechle
2001-01-29 15:03 ` Maciej W. Rozycki
2001-01-26 20:01 ` Jun Sun
2001-01-26 20:38 ` Joe deBlaquiere
2001-01-26 21:02 ` Jun Sun [this message]
2001-04-04 22:13 ` Florian Lohoff
2001-02-19 13:11 ` strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call) Wichert Akkerman
2001-02-19 19:52 ` newbie question Can Altineller
2001-02-20 7:06 ` David Jez
2001-02-20 20:26 ` Mike McDonald
2001-02-20 20:30 ` nick
2001-02-20 20:53 ` Ralf Baechle
2001-02-20 20:41 ` strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call) Ralf Baechle
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=20010126130257.I9325@mvista.com \
--to=jsun@mvista.com \
--cc=jadb@redhat.com \
--cc=linux-mips@oss.sgi.com \
/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.