From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4341FC4332F for ; Sun, 13 Nov 2022 18:32:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:References:Cc:To:From: Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=rsoNkbgtHna+LMVauitvw+rbq35L5a43aXinX69gunM=; b=XHPiEHsV4PaUQG W+LhscNeaKv5OG8TAap1RdsRxLEwJUYQ/NL7wLnZOiO1NOE2ZNUWcniqWd8zP7QAX8K1eoWT3/ItF mc8kO6xOI0nbNwMOhFYZRaBkpEmjzb4ER5rpPC5neHa2bBAy2sK8o0/1KQi5VjCqVi3hKHL/Pt+gR nGum07mUvYHEJYOEdL0KUaI70fip6XPLjVsBezj4XgOUnF0AhU2tP2e9y+tM6n1MTtJGrg9v1bNZt a5dlLBh+ktmH+8IHn39J1ILl8FzAL3kZydWJMVdN6mj6043oPF7HS8N9yk3BlDBsKT3mak84Zg1Yn vtlqeb/NFvcguzSi+zEQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ouHlg-00CzSX-VE; Sun, 13 Nov 2022 18:31:45 +0000 Received: from wp530.webpack.hosteurope.de ([80.237.130.52]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ouHld-00CzQi-E3 for linux-arm-kernel@lists.infradead.org; Sun, 13 Nov 2022 18:31:43 +0000 Received: from [2a02:8108:963f:de38:eca4:7d19:f9a2:22c5]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1ouHla-0006Tq-Kg; Sun, 13 Nov 2022 19:31:38 +0100 Message-ID: <0f936a56-29af-49d8-f291-398e91cce0e2@leemhuis.info> Date: Sun, 13 Nov 2022 19:31:37 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.1 Subject: Re: [Issue] EFI runtime-wrapper is broken #forregzbot Content-Language: en-US, de-DE From: Thorsten Leemhuis To: linux-arm-kernel Cc: linux-efi References: <34d7f903-9d1a-d63b-0d32-b72ae775f26a@leemhuis.info> In-Reply-To: <34d7f903-9d1a-d63b-0d32-b72ae775f26a@leemhuis.info> X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1668364301;2fb03d76; X-HE-SMSGID: 1ouHla-0006Tq-Kg X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221113_103141_645535_AFD807A7 X-CRM114-Status: GOOD ( 22.25 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org [Note: this mail is primarily send for documentation purposes and/or for regzbot, my Linux kernel regression tracking bot. That's why I removed most or all folks from the list of recipients, but left any that looked like a mailing lists. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter out.] On 08.11.22 13:26, Thorsten Leemhuis wrote: > Hi, this is your Linux kernel regression tracker. CCing the regression > mailing list, as it should be in the loop for all regressions, as > explained here: > https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html > > On 28.10.22 11:39, Ard Biesheuvel wrote: >> On Fri, 28 Oct 2022 at 11:38, Gavin Shan wrote: >>> On 10/28/22 5:21 PM, Ard Biesheuvel wrote: >>>> On Fri, 28 Oct 2022 at 11:10, Gavin Shan wrote: >>>>> I ran into the following crash with v6.1.rc2. I'm not sure if it's known >>>>> issue. Last good version is v6.0.rc6/rc7. The kernel configuration is attached. >>>> >>>> This is probably related to the patch below. It means the firmware is >>>> buggy, and does not work as it should if the firmware never calls >>>> SetVirtualAddressMap() [and doing so is explicitly described as >>>> OPTIONAL by the EFI specification]. >>>> >>>> The problem here is that other EFI implementations (primarily the >>>> Qualcomm ones used on Windows-on-ARM laptops) are buggy too, and don't >>>> tolerate SetVirtualAddressMap(). >>>> >>>> Can you try whether reverting the patch below helps? >>> >>> I ran into the issue on server, equipped with Ampere CPUs. With d3549a938b73 >>> reverted, the crash disappeared. >> >> Thanks for confirming >> >> Can you please share the complete boot log and the DMI/SMBIOS data? Thanks. > > Gavin, did you ever send this? > > Or Ard, was there any progress to get the issue fixed? > > I ask because I have this on the list of tracked regression -- and I > noticed there is another report about problems caused by d3549a938b73 > now from Alexandru Elisei: > https://lore.kernel.org/lkml/Y2lAB508TrrjpDPi@monolith.localdoman/ #regzbot fixed-by: 550b33cfd445296 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel