Re: pg11.1: dsa_area could not attach to segment

From: Jakub Glapa <jakub(dot)glapa(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Rick Otten <rottenwindfish(at)gmail(dot)com>, Sand Stone <sand(dot)m(dot)stone(at)gmail(dot)com>, Fabio Isabettini <fisabettini(at)voipfuture(dot)com>, Arne Roland <A(dot)Roland(at)index(dot)de>, Maksim Milyutin <milyutinmagmailcom(at)telsasoft(dot)com>, Sergei Kornilov <sk(at)zsrv(dot)org>
Subject: Re: pg11.1: dsa_area could not attach to segment
Date: 2019-02-06 19:32:38
Message-ID: CAJk1zg2rO7Sv=vmZKGiDzco6p1imd=nh6ToYrNj8sBru8-LOHw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> It might be interesting to have CPU info, too.

model name : Intel(R) Xeon(R) CPU E5-2637 v4 @ 3.50GHz (virtualized
vmware)
and
model name : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz (bare metal)

--
regards,
pozdrawiam,
Jakub Glapa

On Wed, Feb 6, 2019 at 7:52 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:

> On Wed, Feb 06, 2019 at 06:37:16PM +0100, Jakub Glapa wrote:
> > I'm seeing dsa_allocate on two different servers.
> > One is virtualized with VMWare the other is bare metal.
>
> Thanks. So it's not limited to vmware or VM at all.
>
> FYI here we've seen DSA errors on (and only on) two vmware VMs.
>
> It might be interesting to have CPU info, too.
>
> For us the affected servers are:
>
> Intel(R) Xeon(R) CPU E5-2470 0 @ 2.30GHz stepping 02
> microcode: CPU0 sig=0x206d2, pf=0x1, revision=0xb00002e
>
> Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz stepping 02
> microcode: CPU0 sig=0x206d2, pf=0x1, revision=0x710
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2019-02-06 20:09:54 Re: Commit Fest 2019-01 is now closed
Previous Message Ibrar Ahmed 2019-02-06 19:08:57 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)