From: John David Anglin <dave.anglin@bell.net>
To: Carlo Pisani <carlojpisani@gmail.com>, Meelis Roos <mroos@linux.ee>
Cc: 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 09:37:09 -0400 [thread overview]
Message-ID: <63286d01-212f-aa26-cc57-8831dd3ded99@bell.net> (raw)
In-Reply-To: <CA+QBN9AfShbQ1JbcEMr++roxH0oivnEq-ndKc5yt6tGRos+N_w@mail.gmail.com>
On 2019-05-12 6:51 a.m., Carlo Pisani wrote:
>> Problems from test like this suggest a problem outside the libata drivers themselves.
>> To me, it sounds rather something like dma mapping/sync errors, or memory
>> management errors (possibly dependent on hppa bus(bridge types).
> It's not installed in our C3600 at the moment,
> but it seems what we observed 2 days ago with Highpoint RocketRAID
> 1640HTP374 card
> it's PCI 32bit, 4 SATA channels, it doesn't crash, but it randomly
> offers file corruptions.
> The dmseg shows a lot of DMA errors.
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.
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2019-05-12 13:37 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 [this message]
2019-05-12 13:45 ` Carlo Pisani
2019-05-12 14:31 ` John David Anglin
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=63286d01-212f-aa26-cc57-8831dd3ded99@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