From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id C36673858423 for ; Fri, 14 Jan 2022 18:13:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C36673858423 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-575-1w4zzIEqNuypjoFPKlSR1g-1; Fri, 14 Jan 2022 13:13:32 -0500 X-MC-Unique: 1w4zzIEqNuypjoFPKlSR1g-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 16EB58042E0; Fri, 14 Jan 2022 18:13:31 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.49]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 11A9C10A33C9; Fri, 14 Jan 2022 18:13:18 +0000 (UTC) From: Florian Weimer To: "H.J. Lu" Cc: "Carlos O'Donell via Libc-alpha" , "Carlos O'Donell" Subject: Re: glibc 2.35 failures in elf/tst-cpu-features-cpuinfo-static. References: <056482b8-d413-2e24-a546-98ea46e68710@redhat.com> <87ee5aqmla.fsf@oldenburg.str.redhat.com> Date: Fri, 14 Jan 2022 19:13:17 +0100 In-Reply-To: (H. J. Lu's message of "Fri, 14 Jan 2022 10:05:22 -0800") Message-ID: <87tue6p4n6.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-6.4 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2022 18:13:38 -0000 * H. J. Lu: > On Fri, Jan 14, 2022 at 9:00 AM Florian Weimer wrote= : >> >> * Carlos O'Donell via Libc-alpha: >> >> > Checking HAS_CPU_FEATURE (RTM): >> > HAS_CPU_FEATURE (RTM): 1 >> > cpuinfo (rtm): 0 >> > *** failure *** >> >> Could you pin this test to specific CPUs and see if it behaves >> differently depending on the CPU? >> > > Hi Carlos, > > I believe you ran into: > > https://sourceware.org/bugzilla/show_bug.cgi?id=3D28033 > https://www.intel.com/content/www/us/en/support/articles/000059422/proces= sors.html > > Specifically your CPU is listed as > > 06_9EH <=3D0xC 8th/9th Generation Intel=C2=AE Core=E2=84=A2 Processors an= d Intel=C2=AE > Pentium=C2=AE Processors based on Coffee Lake microarchitecture > > I think we should black list all CPUs on the list. I think Siddhesh ran into this before, after laptop suspend. It's a firmware or kernel bug that the CPUID state across cores is inconsistent after suspend. It's not a glibc issue. Thanks, Florian