From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Arto Jantunen <viiru@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] SMP problems (hardware gurus, please read)
Date: Thu, 12 Sep 2002 12:49:43 -0600 [thread overview]
Message-ID: <20020912184943.99E5C4829@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Arto Jantunen <viiru@debian.org> of "Thu, 12 Sep 2002 12:10:18 +0300." <20020912091018.GA16372@dt-link.fi>
Arto Jantunen wrote:
> > Also, are there any HP hardware gurus out there that can explain these odd
> > io numbers? Could they be relevant?
Yes, I need to find the right docs to decode the meaning though.
I've not been motivated to chase this lately.
A few more observsation about HPMC problems:
o A500-55 and A500-44 don't have this problem.
o SMP kernel on 1 CPU and UP kernel on the same box *should* do exactly
the same things besides aquire/release spinlocks. This suggests someone
fixed something in the non-SMP code path and missed the SMP part.
> I did this, but the stuff I got from ser pim is almost all zeroes.
> I'm attaching it anyway, but I don't think it is correct. I rebooted
> by shutting it down from the power switch, is there a "softer" way
> to do it (I only have a serial console)?
HP9000/800 series machines should all support <ctl>-B
to get to service processor prompt.
"he" for help.
"rs" to reset the machine.
"tc" to capture current state of the machine for debugging "hung" machines.
(TC data is available with "ser pim" output")
hth,
grant
next prev parent reply other threads:[~2002-09-12 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 5:48 [parisc-linux] SMP problems Arto Jantunen
2002-09-12 6:04 ` Ryan Bradetich
2002-09-12 6:52 ` [parisc-linux] SMP problems (hardware gurus, please read) Jeremy Drake
2002-09-12 9:10 ` Arto Jantunen
2002-09-12 18:49 ` Grant Grundler [this message]
2002-09-12 20:12 ` Derek Engelhaupt
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=20020912184943.99E5C4829@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=viiru@debian.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