From: grundler@dsl2.external.hp.com (Grant Grundler)
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Randolph Chung <randolph@tausq.org>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.5 randomly kills applications with page faults
Date: Fri, 20 Dec 2002 15:37:47 -0700 [thread overview]
Message-ID: <20021220223747.GD13478@dsl2.external.hp.com> (raw)
In-Reply-To: <200212202212.gBKMCbv08741@localhost.localdomain>
On Fri, Dec 20, 2002 at 04:12:37PM -0600, James Bottomley wrote:
> The fix is simple: increment the stack pointer. I chose 16 to preserve every
> alignment I can think of is that also safe for 64 bit?
needs to be 64 bytes - lamont confirmed.
> With this fix, my system seems fairly solid. It survives my bitkeeper and
> stress tests so far (about 30 min) previously it always collapsed within
> a few minutes.
excellent!
> P.S. After this little debug frenzy, I don't personally care if I ever see
> another line of parisc assembly again, so if another obscure register
> trashing problem turns up, my good deed is done...
*G*
/me kowtows to the east several times...
> STREG %r1,0(%r30) /* Stick r1 (usp) here for now */
> + ldo 16(%r30),%r30
As David observed, this wants to use ",ma" and I'll work that out with
lamont/helge offline.
Something will get committed to 2.4.x/2.5.x trees this afternoon.
thanks - what a wonderful Christmas present! :^)
grant
next prev parent reply other threads:[~2002-12-20 22:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 16:37 [parisc-linux] 2.5 randomly kills applications with page faults James Bottomley
2002-12-18 17:02 ` Randolph Chung
2002-12-20 22:12 ` James Bottomley
2002-12-20 22:19 ` John David Anglin
2002-12-20 22:37 ` Grant Grundler [this message]
2002-12-22 7:11 ` Grant Grundler
2002-12-22 10:17 ` Helge Deller
2002-12-22 16:35 ` James Bottomley
2002-12-21 1:38 ` Grant Grundler
2002-12-21 1:46 ` James Bottomley
2002-12-21 4:34 ` Grant Grundler
2002-12-21 5:03 ` James Bottomley
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=20021220223747.GD13478@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=James.Bottomley@steeleye.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.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.