From mboxrd@z Thu Jan 1 00:00:00 1970 From: John David Anglin Subject: Re: kernel 4.15.7/64bit, C3600 is unstable during heavy I/O on PCI Date: Sat, 17 Mar 2018 13:47:37 -0400 Message-ID: References: <20180317113655.GA30572@ls3530.fritz.box> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Cc: Carlo Pisani , debian-hppa@lists.debian.org, linux-parisc To: Grant Grundler , Helge Deller Return-path: In-Reply-To: Resent-Message-ID: List-Id: linux-parisc.vger.kernel.org List-Id: List-URL: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Archive: https://lists.debian.org/msgid-search/b2fd86ec-a83a-5133-fa66-29229595851c@bell.net Hi Grant, On 2018-03-17 12:12 PM, Grant Grundler wrote: > "Master Abort" means the MMIO > transaction timed out - usually due to the device not responding to an > MMIO read. In lba_pci.c and sba_iommu.c, it says "BE WARNED: register writes are posted" and need to be followed by a read.  It seems there are a some routines in these modules that have writes that aren't followed by a read.  One is lba_wr_cfg(). Another might be the macro LBA_CFG_RESTORE().  Are these okay? It seems probable that the problem that Carlo is having is a conflict between devices. Dave