public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter 'PMc' Much <[email protected]>
To: Tomas Vondra <[email protected]>
Cc: [email protected]
Subject: Re: Need help debugging SIGBUS crashes
Date: Tue, 17 Mar 2026 16:31:08 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

On Tue, Mar 17, 2026 at 02:54:29PM +0100, Tomas Vondra wrote:
! 
! BTW the first thing I'd try is testing memory with memtest86+ or a
! similar tool. I don't know what hardware you're using, but I recently
! dealt with weird failures on older machines, and it turned out to be
! faulty RAM modules.

Yes, I considered this as one of the first things, and then ruled
it out, because
 A) this is a Haswell-Xeon EP, and not only does it have ECC, but I
    have already seen it identify a bad stick on this very hardware,
 B) given that we have address space randomization, and that the
    postgres memory footprint is kept rather small here (it should
    then use ZFS ARC), I consider it highly unlikely that a memory
    defect would always hit at the very same code-line, and never
    anywhere else or in a different program.

PMc

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Need help debugging SIGBUS crashes
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox