Re: kernel 4.15.7/64bit, C3600 is unstable during heavy I/O on PCI
just a nit on PCI terminology...
On Sat, Mar 17, 2018 at 12:36 PM, Helge Deller <firstname.lastname@example.org> wrote:
> * Carlo Pisani <email@example.com>:
>> I have created and applied the following patch
>> testing the kernel with heavy I/O seems now stable
>> my C3600 is still under testing, moving chunks of 500Mbyte and compiling gcc-v6
> --- drivers/parisc/lba_pci.c 2018-01-28 22:20:33.000000000 +0100
> +++ drivers/parisc/lba_pci.c 2018-03-15 12:26:44.839894952 +0100
> @@ -1405,7 +1405,7 @@
> /* Set HF mode as the default (vs. -1 mode). */
> stat = READ_REG32(d->hba.base_addr + LBA_STAT_CTL);
> - WRITE_REG32(stat | HF_ENABLE, d->hba.base_addr + LBA_STAT_CTL);
> + WRITE_REG32(stat & ~HF_ENABLE, d->hba.base_addr + LBA_STAT_CTL);
> ** Writing a zero to STAT_CTL.rf (bit 0) will clear reset signal
> That's the patch from Kyle:
> which comes out of this mail thread:
> specifically with those notes:
> Citing here:
> "bus timeout" usually means we tried to read an address that doesn't
> respond. that is, nothing on the bus accepted the transaction for it,
> so it timed out and HPMC'd the box.
HF= Hard Fail on PCI "Master Abort". "Master Abort" means the MMIO
transaction timed out - usually due to the device not responding to an
MMIO read. We normally want HF to be enabled as you noted below in
order to get state of the CPU and which IO device it was trying to
It's possible the "~0L" returned in SoftFail mode is being handled by
the driver OR the particular read that fails just doesn't matter.
Would have to see dmesg output if the driver ever complains about
invalid MMIO read data (~0L).
> what you really need is the IIR, and the address it tried to access
> (both the kernel vaddr which will be in the register, and the "system
> requester address" from the hpmc dump which will be the physical address
> not sure why the hpmc handler is getting skipped, that's a little weird.
> you can try hacking elroy to set softfail mode on that bus, which will
> result in a timeout on the pci bus to return -1 (like what x86 and most
> other architectures do) rather than hang the box, but it really likely
> means a driver bug.
> So, you change LBA to return -1 instead of faulting via HPMC which is
> of course one work-around to avoid the HPMC.
> But could you try to check the driver instead?
> You run this SATA controller:
> 01:05.0 RAID bus controller: VIA Technologies, Inc. VT6421 IDE RAID
> Can you maybe try to localize where in the drivers/ata/sata_via.c driver
> triggers the HPMC ?
> --- arch/parisc/kernel/hpmc.S 2018-01-28 22:20:33.000000000 +0100
> +++ arch/parisc/kernel/hpmc.S 2018-03-15 14:13:46.611969815 +0100
> @@ -308,4 +290,5 @@
> .align 4
> .export os_hpmc_size
> - .word .os_hpmc_end-.os_hpmc
> + /* .word .os_hpmc_end-.os_hpmc */
> + .word (.os_hpmc_end - .os_hpmc) * 4 /* sizeof(u32) */
> This one seems wrong.
> I think you just didn't hit a HPMC with your first patch, and as such
> this patch has no influence...