Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp5398303rwl; Sun, 8 Jan 2023 14:31:25 -0800 (PST) X-Google-Smtp-Source: AMrXdXto4qoQvl/dR4pG7eePTzOaZgzBB2Jws2Yzrqz3nVrvuk0ISPd6XMqBigF1kcc9o2bubvGz X-Received: by 2002:a17:907:6e15:b0:7c0:fb3d:11a6 with SMTP id sd21-20020a1709076e1500b007c0fb3d11a6mr67970549ejc.38.1673217084809; Sun, 08 Jan 2023 14:31:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673217084; cv=none; d=google.com; s=arc-20160816; b=Ihu9xje5yWtTvWsWpEyTFv8AIZOQ3rXWjSOd2nhqNWCatOvMpXTYme6LU88RtbniyU 6dIFdBhhxYUXCtgq2+AZKrZJvDGHOE/a6nwjd8bCqIKRIL22RMEsH1Y3qFxW7WqvMo/y ULDNgJRVpahERAoCS+uB3W0pxJMNcCnBSlzOYZWVKFRQkQD6aB5L+AIfK5pB+Yrws7DG cVbsV9iwQcp+OqLwUuOJnSek25049s2hs3noZElGqi3okoiihm0dccdZa6pdBLArPMN4 UFpOJQkufWQF1BXMm2jm4TN5JSV3x3pATIwR43VUg1jfIB4o5cvESDc6uu17e3zMwBEZ Bdyg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=ZQf3Expb1rUJy7Rc44uGIHPD++uoDqXzbvOEJjmuv5w=; b=D3xJ2wqfMtXYKWgY21egqeifWfiEMZRKuhYWnK/ywT2N98OpPEaC/TpNofjlsr1tk0 ZPa668abBqkH39P9AZi3zR020BVd8JpMKOAXImUzm1EMzjq+Bb6s2ZaDc111Xl6xIDXt sWLv8/6vOBX+wq/AuUgh4kjuhUp9FGmTver0JoKVP8fqbgKK5nQ4dQg6O1mZFnGNvEf2 udk1i18TWqMo0BBt81Pscm9RH4ngfWZEBCKvd+Ce5KZQbDwbLeoPaJNfqgSXudRNy/J5 tJx1+gPoquS2k4oLSKpaqSyodUPa5x9Mcez2NasLuwCLA/BMct0ebeqAjBI7jZ/L2Yzc zWQw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="P/96NHTU"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id xi5-20020a170906dac500b007ae1874c142si7834258ejb.446.2023.01.08.14.31.12; Sun, 08 Jan 2023 14:31:24 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="P/96NHTU"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231378AbjAHW1f (ORCPT + 51 others); Sun, 8 Jan 2023 17:27:35 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58566 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233409AbjAHW1e (ORCPT ); Sun, 8 Jan 2023 17:27:34 -0500 Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7AE44312 for ; Sun, 8 Jan 2023 14:27:31 -0800 (PST) Received: by mail-wr1-x432.google.com with SMTP id s9so6457940wru.13 for ; Sun, 08 Jan 2023 14:27:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=ZQf3Expb1rUJy7Rc44uGIHPD++uoDqXzbvOEJjmuv5w=; b=P/96NHTU7SYFmfz1qIfcnv24h7ukpc4hM8EvE5zf/iNQj6s+tjxPXgkxtogtRztR/f IfMUvMww7Qyop7gvTiGvhlG4Ik0wr6jl8WZWeiBw/coZIk9ap26aR9lUGX7ocRcpgUD8 WOCcgAn8A/Rnop0inYzMlyrOz1gK4vppMFE1NIvUdcgV7izG9GTOvMc1pxHhHU3GmLQL ckk9q6cqTdiAFjXYsafBYZy7AMgr2cZmKLS64R4Ptzkb1Jz+aTEIQFgp+m45dRQt3LOa eUVeYjvznkBtcTuvvuR0VYx96pITFG/+2/2zvVnWm7okUTS8iLe+Ng+gosjz9XNu0KIl m78w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ZQf3Expb1rUJy7Rc44uGIHPD++uoDqXzbvOEJjmuv5w=; b=bQvvCZIN2DdFlzzvVt9ONy5gFyTLQnNkvBGp4xsa015OqvjmMGZeA7uJa3yA/MrwBS SZGfB7X9Ch4AIamxcc30DvNbqfDbFFlPqI42g3yi1tkIWYJQ5cZJYx7TmhOY5hhDiTZU NeVkGPsQTwRTs/xrnFqWeDTbyrfQpYlKB6YggGd7BwPDvHAVDkHLo1PtXimQtJkixG88 xZmGH1zaNZFy0WQZqIKR0ws7bZaWqL1FqIOIhdHX0Sqbd1mxQkjxr2a+Hk4Du/eQh52O v4T9n2/6ZlQVhm14k0qJKif1EjKc+kJ+E0mcEvbuGye/Y565sRGM0gPU5pw3rU2oTjte xy1g== X-Gm-Message-State: AFqh2koSpwC7wYJ0k8M0HpDs/SrG83BHk1xhS9igCdq9GgGT9OOIzB+E bsbjgZKXqkp6/4uY1Cvk9ms9dbCo72OqOpH3 X-Received: by 2002:adf:fe87:0:b0:274:fae4:a512 with SMTP id l7-20020adffe87000000b00274fae4a512mr34257258wrr.71.1673216849974; Sun, 08 Jan 2023 14:27:29 -0800 (PST) Received: from solpc.. (67.pool90-171-92.dynamic.orange.es. [90.171.92.67]) by smtp.gmail.com with ESMTPSA id e7-20020a5d5007000000b0023662d97130sm6944485wrt.20.2023.01.08.14.27.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 08 Jan 2023 14:27:29 -0800 (PST) From: Joan Bruguera To: Borislav Petkov Cc: Peter Zijlstra , linux-kernel@vger.kernel.org, x86@kernel.org, Thomas Gleixner Subject: Re: Wake-up from suspend to RAM broken under `retbleed=stuff` Date: Sun, 8 Jan 2023 22:27:28 +0000 Message-Id: <20230108222728.69350-1-joanbrugueram@gmail.com> X-Mailer: git-send-email 2.39.0 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I can also reproduce it on my Ryzen 5700G (both real and QEMU+KVM). So it doesn't appear to be Intel or AMD specific. Perhaps your BIOS/UEFI keeps the value of %gs or it points somewhere valid after waking from suspend to RAM, and the ones I have don't? That's a way I can imagine it not crashing on some HW. If that's the case, you should still be able to reproduce it on QEMU. Or it's also possible that the QEMU issue is different from the one on real HW (though unlikely, I think)