Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grSJW-00046Y-7Q for pgsql-hackers@arkaria.postgresql.org; Wed, 06 Feb 2019 18:52:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1grSJU-0006BM-St for pgsql-hackers@arkaria.postgresql.org; Wed, 06 Feb 2019 18:52:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grSJU-00069g-CY for pgsql-hackers@lists.postgresql.org; Wed, 06 Feb 2019 18:52:48 +0000 Received: from mail-it1-x141.google.com ([2607:f8b0:4864:20::141]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grSJR-00029A-9U for pgsql-hackers@postgresql.org; Wed, 06 Feb 2019 18:52:47 +0000 Received: by mail-it1-x141.google.com with SMTP id z7so8613209iti.0 for ; Wed, 06 Feb 2019 10:52:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=22XJhL4p7TJbUejKG8Sbf42qUgQXR+batKHrJWuBosc=; b=y8m0QdMvFrTl+TGdwRagEmOT7t95d5GVf6+B3Ose46B+Y77wb+17Zo0bebpjblyU+L EvnIX9JxgnCAe67RmoZ4i1ogl4hF9/2YiCSx4O/zyNZKcswqKlNLCBO5cVi+7MX/AOP7 zaPtaUP1XLb3t7BXDATJmdcoGcZ09dMAFe+izoworw7Z+EI4M/dmYq9BeE2lcGRlJgV+ 9lyBbr0bfJFV0mv/JN9M3hLCbpCTlnFhEdLWEyUZg7lLK2s1LyiwG1iXVBguH+wYrX4X RYr8RWk+czKF1wlCM4Wli+yX/LSPnf+3ipe4s10G80IbZRza95hra3RwBg8r+JASGJ0C XDrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=22XJhL4p7TJbUejKG8Sbf42qUgQXR+batKHrJWuBosc=; b=jRxV51UruovFBZ1SAykR0hUXStTToroAVYtyjom/V1ilwPU2KL6OHULSst7wlsEJ7T BZ9OZCawyXnI7+F49acY6i32u6BnJJY21gbnZlSS3I45Rd8YMhNf1AyeoZPZy0LFXjW5 UiHTmElJy7zThRQ9ERSZqa/mMMyWVmsWJZFDXq8ZjZpPLBXD4Z9xZS68iHIpO4ZNnW48 y7f+bbLEWJAtf53wcb8NMVLh23oJ4IbMBMEwmFn2KmkO/rFbmdu97B8Xvo5TaYYnXW7m LQisYJkcS1csCeYTRWBTr7d9lEOvZ6G1Hj7ln5xO6nVsdXqTiDr4h6Qbq4Gz0zPBKFEY gXgQ== X-Gm-Message-State: AHQUAuZvf1SPpjLFCrjTlYexccKwMprxmLUVN3WdzcZ9vJw8pQewzRxu y9PwYDHH6cdftZzCcYVACrdofQ== X-Google-Smtp-Source: AHgI3IbgBsNwbmRn4z/UsCWVcKIRMCsTBDst/xAl1y9g36di2FXq2FU6cJnDbzNUt/YsukpvT2u7xg== X-Received: by 2002:a02:290e:: with SMTP id p14mr6583852jap.74.1549479164414; Wed, 06 Feb 2019 10:52:44 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id t69sm3958095itb.26.2019.02.06.10.52.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Feb 2019 10:52:43 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id AF239800519; Wed, 6 Feb 2019 12:52:41 -0600 (CST) Date: Wed, 6 Feb 2019 12:52:41 -0600 From: Justin Pryzby To: Jakub Glapa Cc: Thomas Munro , Pg Hackers , Rick Otten , Sand Stone , Fabio Isabettini , Arne Roland , Maksim Milyutin , Sergei Kornilov Subject: Re: pg11.1: dsa_area could not attach to segment Message-ID: <20190206185241.GF29720@telsasoft.com> References: <20181231221734.GB25379@telsasoft.com> <20190205163509.GM29720@telsasoft.com> <20190205183454.GS29720@telsasoft.com> <20190206021047.GU29720@telsasoft.com> <20190206171940.GA32624@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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