From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Script for decoding PSR in oopses
Date: Fri, 31 Jan 2003 03:31:43 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805787@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805784@msgid-missing>
>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:
>>>>> On Fri, 31 Jan 2003 13:10:58 +1100, Keith Owens <kaos@ocs.com.au> said:
Keith> On Fri, 31 Jan 2003 12:46:00 +1100, Peter Chubb
Keith> <peter@chubb.wattle.id.au> wrote:
>>> I find trying to work out what the PSR is after an oops to be a
>>> bit of a pain, so here's an awk script to do it for you.
>>> Usage is decode_psr hex_number if you save the script as
>>> decode_psr.
Keith> Below are Perl ia64_psr and ia64_isr. Run as echo hex_number |
Keith> ia64_[pi]sr
David> OK, now where is the Python version?? ;-))
Who cares? Once you've got a script you can use it.
BTW, there's a bug in the AWK script:
--- decode_psr-old 2003-01-31 13:33:51.000000000 +1100
+++ decode_psr 2003-01-31 13:11:13.000000000 +1100
@@ -77,7 +77,7 @@
psr = int(psr / 2)
if (psr % 2 = 1)
decoded = decoded "rt "
- psr = int(psr / 16)
+ psr = int(psr / 32)
cpl = psr % 4;
decoded = decoded "cpl=" cpl " "
next prev parent reply other threads:[~2003-01-31 3:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 1:46 [Linux-ia64] Script for decoding PSR in oopses Peter Chubb
2003-01-31 2:10 ` Keith Owens
2003-01-31 2:31 ` David Mosberger
2003-01-31 3:31 ` Peter Chubb [this message]
2003-01-31 4:41 ` Wichmann, Mats D
2003-01-31 4:56 ` Keith Owens
2003-01-31 5:08 ` David Mosberger
2003-01-31 20:10 ` Jim Hull
2003-02-10 5:12 ` Matt Chapman
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=marc-linux-ia64-105590709805787@msgid-missing \
--to=peter@chubb.wattle.id.au \
--cc=linux-ia64@vger.kernel.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