From: John David Anglin <dave.anglin@bell.net>
To: Carlo Pisani <carlojpisani@gmail.com>
Cc: Meelis Roos <mroos@linux.ee>, Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org
Subject: Re: 5.2 hppa merge seems to work on my machines
Date: Sun, 12 May 2019 10:31:03 -0400 [thread overview]
Message-ID: <5e1ee7c5-9d3e-d221-ce74-c7ae42982f8d@bell.net> (raw)
In-Reply-To: <CA+QBN9DLCT2WGWEPUg4yrOswUkB1PepkbuGnzwEAmxokOgX74g@mail.gmail.com>
On 2019-05-12 9:45 a.m., Carlo Pisani wrote:
>> I agree. The memory errors in the PIM dump are recorded by the PDC firmware and they don't
>> directly involve the linux drivers. Might be hardware problem.
> which kind of error problem?
|Memory Error Log Information:
Timestamp =
Sat May 11 11:37:53 GMT 2019 (20:19:05:11:11:37:53)
'9000/785 B,C,J Workstation Memory Error Log', rev 0, 64 bytes:
This log displays the contents of memory specific registers when the
HPMC occurred. If there are multiple memory errors, the order they are
listed is not indicative of the order they occurred.
Trans Addr
Memory Error Type(s) OV MID ID par CP DIMM Runway Address
-------------------- -- --- ----- ---- -- ------- -------------------
1) Correctable Mem 1 0x6 0x a na na 05 0x 0036c76b40
Syndrome
------------------
1) 0x94
<Press any key to continue (q to quit)>
I/O Module Error Log Information:
Timestamp =
Sat May 11 11:37:53 GMT 2019 (20:19:05:11:11:37:53)
'9000/785 B,C,J Workstation IO Error Log', rev 0, 228 bytes:
Rope Word1 Word2 Word3
------ ------------ ------------
0 0x00000000 0x0e0cc009 0x00000000fed30048
1 0x00000000 0x1e0cc009 0x00000000fed32048
2 ---------- 0x2e0cc009 ------------------
3 ---------- 0x3e0cc009 ------------------
4 0x00000000 0x4e0cc009 0x00000000fed38048
5 ---------- 0x5e0cc009 ------------------
6 0x00000000 0x6e0cc2a9 0x00000000fed3c048
7 ---------- 0x7e0cc009 ------------------
|
>
> those two cards have no problem when tested on PowerMac-G4
> and we have a second C3600, reporting the same behavior
>
> so, supposing those cards are OK, and C3600s are OK
> what might be wrong about the hardware?
>
--
John David Anglin dave.anglin@bell.net
prev parent reply other threads:[~2019-05-12 14:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 14:23 5.2 hppa merge seems to work on my machines Meelis Roos
2019-05-08 18:43 ` Helge Deller
2019-05-10 11:43 ` Carlo Pisani
2019-05-11 10:47 ` Helge Deller
2019-05-11 15:27 ` John David Anglin
2019-05-11 15:43 ` Helge Deller
2019-05-11 17:43 ` Rolf Eike Beer
2019-05-11 18:16 ` Helge Deller
2019-05-11 21:41 ` Carlo Pisani
2019-05-11 22:36 ` John David Anglin
2019-05-12 6:28 ` Carlo Pisani
2019-05-12 16:22 ` John David Anglin
2019-05-12 9:51 ` Meelis Roos
2019-05-12 10:51 ` Carlo Pisani
2019-05-12 13:37 ` John David Anglin
2019-05-12 13:45 ` Carlo Pisani
2019-05-12 14:31 ` John David Anglin [this message]
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=5e1ee7c5-9d3e-d221-ce74-c7ae42982f8d@bell.net \
--to=dave.anglin@bell.net \
--cc=carlojpisani@gmail.com \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=mroos@linux.ee \
/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;
as well as URLs for NNTP newsgroup(s).