Horton

Re: Non-reproducible AIO failure

Thomas Munro <thomas.munro@gmail.com>

View thread
From: Thomas Munro <thomas.munro@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Konstantin Knizhnik <knizhnik@garret.ru>, Alexander Lakhin <exclusion@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-06-18T22:18:21Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. aio: Stop using enum bitfields due to bad code generation

  2. amcheck: Fix posting tree checks in gin_index_check()

  3. aio: Add missing memory barrier when waiting for IO handle

On Thu, Jun 19, 2025 at 4:08 AM Andres Freund <andres@anarazel.de> wrote:
> Konstantin, Alexander, can you share what commit you're testing and what
> precise changes have been applied to the source?  I've now tested this on a
> significant number of apple machines for many many days without being able to
> reproduce this a single time, despite using various compiler
> [versions]. Something has to be different on the two systems you're testing
> on.

What do you see in "System Firmware Version" from "About This Mac" ->
"More Info" -> "General" -> "System Report"?  My M4 Air running
Sequoia 15.5 shows "11881.121.1".  My M1 Air is still running Sequoia
15.4.1 and shows "11881.101.1" (will upgrade it shortly).  The version
before, Sequoia 15.4 (no ".1") actually broke my M1 Air for a couple
of weeks, there was something funny going on with the firmware
involving a kernel panic that mentioned t6000dart (I believe that is
the IOMMU, ie virtual memory hardware for IO), fixed by 15.4.1.  It's
just a paranoid thought, but I wonder if all that stuff rolls out in
sync across all territories.

I have also not managed to reproduce this issue despite running for
many hours yesterday...