linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@freenet.de>
To: device-mapper development <dm-devel@redhat.com>,
	Milan Broz <mbroz@redhat.com>, Ondrej Kozina <okozina@redhat.com>
Cc: linux-pci <linux-pci@vger.kernel.org>,
	Mike Snitzer <msnitzer@redhat.com>,
	mpatocka@redhat.com
Subject: Re: [dm-devel] AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
Date: Thu, 30 Jul 2015 22:30:21 +0200	[thread overview]
Message-ID: <55BA895D.30509@maya.org> (raw)
In-Reply-To: <55B90C25.8030502@maya.org>

On 07/29/2015 at 07:23 PM Andreas Hartmann wrote:
> On 07/29/2015 at 08:41 AM Milan Broz wrote:
>> On 07/29/2015 08:17 AM, Ondrej Kozina wrote:
>>> On 07/28/2015 11:24 PM, Mike Snitzer wrote:
>>>>>
>>>>> I am willing to do tests if you have any idea to be tested - I can
>>>>> reproduce it quite easily.
>>>>
>>>> You can try disabling dm-crypt's parallelization by specifying these 2
>>>> features: same_cpu_crypt submit_from_crypt_cpus
>>>>
>>>
>>> Hi,
>>>
>>> please try adding follwoing cryptsetup perf. options while unlocking 
>>> your LUKS containers: --perf-submit_from_crypt_cpus and 
>>> --perf-same_cpu_crypt.
>>>
>>> Perhaps focus on SSD disk as previous unresolved report mentioned SSD too
> 
> I'll next try to just boot from the rotational disk. If the problem
> doesn't show up here, it could be SSD related, too.
> 
>>
>> Just you need to use cryptsetup 1.6.7 version (older versions do not have this options yet).
> 
> Thanks for this hint.
> 
> I compiled this version and applied it and verified it, if it's really
> in initrd. It was in initrd and the additional options where applied, too.
> 
> But: nothing changed with enabled ncq - exactly same problem as before
> (w/ linux 3.19.8 + additional patches and Linux 4.1 - no difference in
> behavior).


Next tests:
I didn't mount any filesystem on bootup located on the ssd (only the
rotational based mounts) -> no problem.

Next: I tried to add the partitions from the ssd to be mounted on boot -
one by one. As there where 4 partitions to be mounted from the ssd, the
errors came up again.

Next: You suspect the ssd as being bad. Therefore, I changed the ssd and
tested with KINGSTON SV300S37A240G. Result: Same as above - errors are
coming up if there are mounted more than 3 partitions at the same time.


Summary:
- --perf-submit_from_crypt_cpus --perf-same_cpu_crypt -> broken anyway
- rotational disks alone: it's ok
- more than 3 partitions on ssd Corsair Force GT -> broken
- more than 3 partitions on ssd KINGSTON SV300S37A240G -> broken



Regards,
Andreas

  reply	other threads:[~2015-07-30 20:32 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 17:40 AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0 Andreas Hartmann
2015-07-28 17:50 ` Mike Snitzer
2015-07-28 18:20   ` Andreas Hartmann
2015-07-28 18:58     ` Mike Snitzer
2015-07-28 19:23       ` Andreas Hartmann
2015-07-28 19:31         ` Mike Snitzer
2015-07-28 20:08           ` Andreas Hartmann
2015-07-28 21:24             ` Mike Snitzer
2015-07-29  6:17               ` [dm-devel] " Ondrej Kozina
2015-07-29  6:41                 ` Milan Broz
2015-07-29 17:23                   ` Andreas Hartmann
2015-07-30 20:30                     ` Andreas Hartmann [this message]
2015-07-31  7:23                       ` Milan Broz
2015-07-31  7:55                         ` Andreas Hartmann
2015-07-31  8:15                           ` Andreas Hartmann
2015-07-31  8:28                           ` Milan Broz
2015-07-29 10:37               ` Milan Broz
2015-07-28 18:56   ` Andreas Hartmann
2015-07-28 19:29     ` Mike Snitzer
2015-08-01 14:20       ` [dm-devel] " Andreas Hartmann
2015-08-02 13:38         ` Andreas Hartmann
2015-08-02 17:57           ` Mikulas Patocka
2015-08-02 18:48             ` Andreas Hartmann
2015-08-03  8:12               ` Joerg Roedel
2015-08-04 14:47                 ` Mike Snitzer
2015-08-04 16:10                   ` Jeff Moyer
2015-08-04 18:11                     ` Andreas Hartmann
2015-08-07  6:04                       ` Andreas Hartmann
2015-09-20  6:50             ` [dm-devel] " Andreas Hartmann
2015-09-29 15:21               ` Joerg Roedel
2015-09-29 15:58                 ` Mikulas Patocka
2015-09-29 16:20                   ` Joerg Roedel
2015-09-30 14:52                     ` Andreas Hartmann
2015-10-06 10:13                       ` Joerg Roedel
2015-10-06 18:37                         ` Andreas Hartmann
2015-10-07 15:40                           ` Joerg Roedel
2015-10-07 17:02                             ` Andreas Hartmann
2015-10-08 17:30                               ` Joerg Roedel
2015-10-08 18:59                                 ` Andreas Hartmann
2015-10-08 19:47                                   ` Andreas Hartmann
2015-10-09 10:40                                     ` Joerg Roedel
2015-10-09 14:45                                     ` [PATCH] iommu/amd: Fix NULL pointer deref on device detach " Joerg Roedel
2015-10-09 17:42                                       ` Andreas Hartmann
     [not found]                           ` <56148A1B.5060506@maya.org>
2015-10-07 16:10                             ` [dm-devel] AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: " Joerg Roedel
2015-10-07 16:52                               ` Andreas Hartmann
2015-10-08 16:39                                 ` Joerg Roedel
2015-10-08 18:21                                   ` Andreas Hartmann
2015-10-08 19:52                                     ` Andreas Hartmann
2015-10-09  5:20                                       ` Andreas Hartmann
2015-10-09  9:15                                         ` Andreas Hartmann
2015-10-09 14:59                                           ` Joerg Roedel
2015-10-09 17:46                                             ` Andreas Hartmann
2015-10-11 12:23                                               ` Andreas Hartmann
2015-10-12 12:07                                                 ` Andreas Hartmann
2015-10-12 12:34                                               ` Mikulas Patocka

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=55BA895D.30509@maya.org \
    --to=andihartmann@freenet.de \
    --cc=dm-devel@redhat.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mbroz@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=msnitzer@redhat.com \
    --cc=okozina@redhat.com \
    /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).