From: Ralf Baechle <ralf@oss.sgi.com>
To: Ryan Martindale <ryan@qsicorp.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Problem with gp
Date: Wed, 31 Jul 2002 21:04:23 +0200 [thread overview]
Message-ID: <20020731210423.E4892@dea.linux-mips.net> (raw)
In-Reply-To: <3D482FF3.11F8CA0B@qsicorp.com>; from ryan@qsicorp.com on Wed, Jul 31, 2002 at 11:44:03AM -0700
On Wed, Jul 31, 2002 at 11:44:03AM -0700, Ryan Martindale wrote:
> I seem to be having troubles getting the CVS snapshot up and running.
> I've debugged it, and it seems that the problem stems from the fact that
> $28 (gp) is modified in the SAVE_SOME macro to point to somewhere on the
> stack (not sure why this occurs). Anyways, when I get my first system
> timetick interrupt, the update_process_times function fails to get the a
> valid task structure pointer and wipes out. Why are we adjusting gp
> here, since it is explicitly expected to hold only current_thread_info?
Are you using 2.5 by chance? 2.5.x is currently pretty unstable as I'm
porting all the major changes in the upstream sources to MIPS. I recommend
to stick with 2.4 for now.
Ralf
next prev parent reply other threads:[~2002-07-31 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 18:44 Problem with gp Ryan Martindale
2002-07-31 19:04 ` Ralf Baechle [this message]
2002-08-01 0:04 ` Ryan Martindale
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=20020731210423.E4892@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=ryan@qsicorp.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.