Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] testing HP-PA risc hardware
Date: Fri, 1 Aug 2003 16:39:18 +0200	[thread overview]
Message-ID: <20030801143918.GI1873@lug-owl.de> (raw)
In-Reply-To: <03Aug1.164945cest.119089@ns.hiscom.nl>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

On Fri, 2003-08-01 16:29:35 +0200, Beerse, Corne <c.beerse@torex-hiscom.nl>
wrote in message <03Aug1.164945cest.119089@ns.hiscom.nl>:
> At first, we suspected the boot disk since its led keeps buring. However,
> booting HP-UX from CDRom for a new fresh install, the boot of the kernel
> crashes at roughly the same point, even with all disks removed. Hence we
> suspected the core memory. However, changing or replacing the memory does
> not change anything in the behavoure.

HP machines do quite some checks on their own on power-up (if you don't
configure them to omit these) and you can get all that from the
INformation (IIRC) command.

I have upgraded one of my boxes these days and a RAM module wasn't
mounted properly. That was reported, as well as it's position:)

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-01 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 14:29 [parisc-linux] testing HP-PA risc hardware Beerse, Corne
2003-08-01 14:39 ` Jan-Benedict Glaw [this message]
2003-08-01 15:04 ` Joel Soete

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=20030801143918.GI1873@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=parisc-linux@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