From: Kirk Bresniker <kirkb@chrome.rose.hp.com>
To: adevries@thepuffingroup.com
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] booting problems
Date: Wed, 09 Jun 1999 23:20:40 PDT [thread overview]
Message-ID: <199906100620.XAA03156@chrome.rose.hp.com> (raw)
In-Reply-To: <375F482D.E1E0B53D@thepuffingroup.com>; from "Alex deVries" at Jun 10, 99 1:07 am
Alex --
| is stuck on. According to the inside of the top cover (oh, what a great
| place to put debug info), this means: "System board fault, HPMC or
| Unknown fault". At this point I'm going for the third.
|
| Looks like we just need to compare a large chunk of the bootable binary
| to figure out what's happening.
|
Not so fast, there is probably more data to be had. Discounting the system
board or unknown faults, you code has caused an HPMC, High Priority
Machine Check. This could be several things, but a good guess would be
either execution of an invalid instruction (you jumped into data), or
you attempted to read a address where there is no hardware to respond.
The way to check is to reboot the system through self-test and when you
reach the boot console handler execute a "SER PIM" command. PIM is an
area of non-volatile memory that is filed in by the routine which
handled the HPMC and is filled with the state of the machine when the
HPMC was encountered. From this you should be able to obtain the
address of the instruction which was executing when the problem occured,
and should be able to determine what type of problem occured (illegal
instruction, bad memory reference, etc.) The PIM dumps are timestamped,
so make sure that your system time is up to date and that that the PIM
is from your crash.
Do your systems include remote management cards? The remote management
cards offer the ability to force a PIM dump through a TC (Transfer of
Control) command, or to force a reset. They also will display chassis
codes. Chassis codes, see the PDC_CHASSIS call in your pdc32.pdf
documentation), are displayed on the 25th line of an HPTERM compatible
terminal or web console session. They are communicated to the management
cards over a dedicated hardware interface, and so inserting them into
your code gives a very low level way to display debug data.
KMB
--
+============================================================+
| Kirk Bresniker (916) 785-5677 |
| 8000 Foothills Blvd |
| Roseville, CA 95747-5649 |
| kirkb@rose.hp.com |
next prev parent reply other threads:[~1999-06-10 6:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-10 5:07 [parisc-linux] booting problems Alex deVries
1999-06-10 6:20 ` Kirk Bresniker [this message]
1999-06-10 7:21 ` Alex deVries
1999-06-10 15:26 ` Kirk Bresniker
1999-06-10 17:08 ` Stan Sieler
1999-06-10 17:03 ` Stan Sieler
1999-06-10 21:20 ` John David Anglin
1999-06-11 7:36 ` Alex deVries
1999-06-11 8:57 ` Alex deVries
1999-06-11 9:08 ` Jeffrey A Law
1999-06-11 14:06 ` John David Anglin
1999-06-11 17:19 ` Alex deVries
1999-06-11 18:10 ` Kirk Bresniker
[not found] <no.id>
1999-06-10 18:32 ` Stan Sieler
-- strict thread matches above, loose matches on Subject: below --
1999-06-10 21:06 Richard J. Rauenzahn
1999-06-11 18:49 Jason Eckhardt
1999-06-11 19:37 ` Alex deVries
1999-06-12 0:56 ` John David Anglin
1999-06-12 1:25 ` John David Anglin
1999-06-12 3:23 ` John David Anglin
1999-06-12 3:43 ` Jeffrey A Law
1999-06-12 5:10 ` Alex deVries
1999-06-12 5:11 ` Jeffrey A Law
[not found] <3761F335.ADA76678@thepuffingroup.com>
1999-06-12 6:32 ` Jeffrey A Law
1999-06-12 11:15 ` Alex deVries
1999-06-12 16:57 ` John David Anglin
1999-06-12 18:36 ` Alan Cox
1999-06-12 18:53 ` Jeffrey A Law
1999-06-12 19:36 ` Matthew Wilcox
1999-06-12 21:15 ` Jeffrey A Law
1999-06-12 21:09 ` Jeffrey A Law
1999-06-13 19:10 ` John David Anglin
1999-06-14 0:17 ` Alex deVries
2001-08-31 16:06 James Waterhouse
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=199906100620.XAA03156@chrome.rose.hp.com \
--to=kirkb@chrome.rose.hp.com \
--cc=adevries@thepuffingroup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox