[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-bugs
Subject:    Re: aarch64: ahci0: log page read failed, slot 31 was still active
From:       Kurt Miller <kurt () intricatesoftware ! com>
Date:       2019-10-26 20:46:03
Message-ID: 1572122763.8246.410.camel () intricatesoftware ! com
[Download RAW message or body]

On Fri, 2019-10-11 at 10:21 +1000, Jonathan Matthew wrote:
> On Mon, Oct 07, 2019 at 01:30:52PM -0400, Kurt Miller wrote:
> > 
> > > 
> > > I hit the issue again using the latest snapshot which
> > > includes the work-around.
> > > 
> > > ahci0: log page read failed, slot 31 was still active.
> > > ahci0: stopping the port, softreset slot 31 was still active.
> > > ahci0: failed to reset port during timeout handling, disabling it
> > > 
> > > No panic this time.
> > > 
> > > The work-around helped with stability in the RAMDISK env where
> > > it was very unstable. Perhaps it is still a good idea.
> > > 
> > This time I got a panic so perhaps there's something helpful
> > in the info below. I had 2x rm -rf on some larger directories
> > going at the time of this panic:
> I've been running a similar load on a desktop pc (amd64), copying and deleting
> ports trees, 4 in parallel, ~4k iops on average, on a SATA SSD through an
> ASM1061 card (looks exactly the same as the one in the pine64 store) for
> around a day with no problems at all.

I purchased a different AHCI SATA controller to see if
the problem continued with a different chipset. The new
card is Marvell 88SE9128 based (StarTech PEXSAT32). It has
been stable for me through a few days of testing, whereas
the ASMedia ASM1061 AHCI card would have crashed several
times under similar conditions. I think this points to
the ASMedia card perhaps needing some quirk.

-Kurt

[prev in list] [next in list] [prev in thread] [next in thread]