Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: parisc-linux@lists.parisc-linux.org
Cc: James.Bottomley@SteelEye.com
Subject: [parisc-linux] 2.5 randomly kills applications with page faults
Date: Wed, 18 Dec 2002 10:37:05 -0600	[thread overview]
Message-ID: <200212181637.gBIGb5r02708@localhost.localdomain> (raw)

I find when booting 2.5.51 up on a C380 that applications seem to take random 
page faults and die.  It seems that the more heavily an application does file 
accesses, the more likely it is to suffer from this.

In debugging the problems, so far it has always been stack manipulation 
instructions in the user level code causing this.  Further, on adding a 
register dump to the page fault debugging code, the reason is that the stack 
pointer is way out of where it should be for a user process (around 0x4f000), 
so I surmise it got clobbered on a rare return path from kernel to user.

Does anyone have any additional information and pointers?  I'm trying to audit 
entry.S to see if there is a little used path that can clobber the stack, but 
my parisc assembly isn't the best...

James

             reply	other threads:[~2002-12-18 16:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-18 16:37 James Bottomley [this message]
2002-12-18 17:02 ` [parisc-linux] 2.5 randomly kills applications with page faults Randolph Chung
2002-12-20 22:12   ` James Bottomley
2002-12-20 22:19     ` John David Anglin
2002-12-20 22:37     ` Grant Grundler
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=200212181637.gBIGb5r02708@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=parisc-linux@lists.parisc-linux.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