linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Carlo Pisani <carlojpisani@gmail.com>, Helge Deller <deller@gmx.de>
Cc: linux-parisc@vger.kernel.org
Subject: Re: 5.2 hppa merge seems to work on my machines
Date: Sun, 12 May 2019 12:51:08 +0300	[thread overview]
Message-ID: <57fc8e0d-c04d-e82e-04ad-2debec0284fb@linux.ee> (raw)
In-Reply-To: <CA+QBN9AZzuJe600ngavoVseRFHCBh4ws5-5pHoWEQkkqZ_wU5g@mail.gmail.com>

> 1) copy a very big file cp data_16GB.bin copy.bin
> 2) compare the md5sum for checking the integrity

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).

-- 
Meelis Roos

  parent reply	other threads:[~2019-05-12  9:51 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 [this message]
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

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=57fc8e0d-c04d-e82e-04ad-2debec0284fb@linux.ee \
    --to=mroos@linux.ee \
    --cc=carlojpisani@gmail.com \
    --cc=deller@gmx.de \
    --cc=linux-parisc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).