From: LaMont Jones <lamont@security.hp.com>
To: Grant Grundler <grundler@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com, lamont@security.hp.com
Subject: Re: [parisc-linux] 715/100 data page fault and msg output
Date: Thu, 16 Sep 1999 16:44:38 -0600 [thread overview]
Message-ID: <19990916224438.6F3BB18711@security.hp.com> (raw)
In-Reply-To: Your message of "Thu, 16 Sep 1999 14:58:14 PDT." <199909162158.OAA21289@milano.cup.hp.com>
> IAOQ: c0067c4c c0067c50
> ISR: 00000000 IOR: c00167a8 IIR: 02a008b8
> ior 00000004
> o In this case the offending instruction and a stack trace.
Interestingly, IIR (the interupting instruction register) contains
mfctl ior,arg2, which is not what we want... Likewise IOR (as
opposed to ior) also looks suspect. I would wager that someone is
not saving the I* registers correctly...
lamont
next prev parent reply other threads:[~1999-09-16 22:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-16 21:58 [parisc-linux] 715/100 data page fault and msg output Grant Grundler
1999-09-16 22:32 ` Philipp Rumpf
1999-09-16 23:22 ` Grant Grundler
1999-09-16 23:32 ` Philipp Rumpf
1999-09-17 1:05 ` Ryan Bradetich
1999-09-17 1:34 ` [parisc-linux] C200 support Grant Grundler
1999-09-17 3:02 ` Ryan Bradetich
1999-09-16 22:44 ` LaMont Jones [this message]
1999-09-16 22:55 ` [parisc-linux] 715/100 data page fault and msg output Philipp Rumpf
1999-09-17 1:39 ` LaMont Jones
1999-09-17 1:52 ` Philipp Rumpf
1999-09-17 21:48 ` Grant Grundler
1999-09-22 11:48 ` [parisc-linux] 715/80 problems Hannu Martikka
1999-09-22 13:35 ` Philipp Rumpf
1999-09-22 14:27 ` Hannu Martikka
1999-09-22 14:29 ` Philipp Rumpf
1999-09-22 14:31 ` Grant Grundler
1999-09-22 15:15 ` Hannu Martikka
1999-09-22 17:00 ` Alex deVries
1999-09-22 13:42 ` Grant Grundler
1999-09-22 15:18 ` Hannu Martikka
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=19990916224438.6F3BB18711@security.hp.com \
--to=lamont@security.hp.com \
--cc=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.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.