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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 97DE1EB64DC for ; Mon, 3 Jul 2023 13:26:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231459AbjGCNZ7 (ORCPT ); Mon, 3 Jul 2023 09:25:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49434 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231559AbjGCNZv (ORCPT ); Mon, 3 Jul 2023 09:25:51 -0400 Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA60BE7B for ; Mon, 3 Jul 2023 06:25:49 -0700 (PDT) Received: by mail-pl1-x62c.google.com with SMTP id d9443c01a7336-1b88e99673eso7209465ad.0 for ; Mon, 03 Jul 2023 06:25:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688390749; x=1690982749; h=content-transfer-encoding:subject:from:cc:to:content-language :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=Ga6xNVvtp+lNzVIC5GM49mPA6xqLDAki2KCiSYDekHg=; b=ByElqpxaXLmLNtmWy2TYSJO/JUFTGZy2h49CLboWSt/xi11ecZfZ0ehCMNkPnbtmoT WXfPqsIo0AqSit+UQaDRRb2wsE1jDsK7ggXZA0jvOsJXqDKt/amZ4wVhd7jU4b3LIDHz vcnn6hrg+41HOaENnZtgt+OmMMJkmr+9KEm8y4q3T/3qmgQFVrKdPg5OcpOlktQECzeE 3QKrviG2Y6o81oyLc5pmwupobhwSvT7bP63ogRAzvzknIF8IW/B3/gRMciHy4gysaqVf 6NeADxjR+CglePxOO7t6ZZHhDT47VrVK33Q8tNl1V4P3vpPJ1/Ozd4RNiP584TD01Y5g hhvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688390749; x=1690982749; h=content-transfer-encoding:subject:from:cc:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=Ga6xNVvtp+lNzVIC5GM49mPA6xqLDAki2KCiSYDekHg=; b=UjXrd3rvaXk49OL5oyG0Y9WdmEnYNUz7KAnAVmF4JOYHqAo9BIKLhGrE66s2nSb1uX BSJW6aiSXlfm9SovwZgIlOv0geUKqjZD+YqAdrsS9uDf8W3L3qZf7wjglFMMwUEZ4m93 KUpTYR8G1EDHTH6Cngz0v+9HTjQxM+XyBwTuAFZUj9jhXDDEwf0h4SGrRHcal2WDIJML q3CpRRiYw/D242YL7+RF1nTaq32a1kGn1FCYpKc6p1v3uN1ti/Gbv3z13DA5pqjmdKTh CKcnCBa3O+BlbckYxMPMAde6/B+d0jbxjajvFQuVh6oCIIxkmzfv2Dru8IrB00ydlBq5 18+A== X-Gm-Message-State: ABy/qLaokUyI5bs4tTvHq4ys+0xq0CliI6OZmovrVnVvkcErCxtAzlQE 63R0T2FWbl0+4SFmXIX+4rtPY5pCmiZypyKu X-Google-Smtp-Source: APBJJlGJ2K9GY+2bcZXbHVRCdunLIb1dR6F7DBiszDdzV3UC3p3rDMFzkNgSX8R+ppFGaZyRzNTATA== X-Received: by 2002:a17:903:1c9:b0:1b8:76cb:3e50 with SMTP id e9-20020a17090301c900b001b876cb3e50mr6928046plh.47.1688390749077; Mon, 03 Jul 2023 06:25:49 -0700 (PDT) Received: from [192.168.0.103] ([103.131.18.64]) by smtp.gmail.com with ESMTPSA id jl23-20020a170903135700b001aafa2e212esm15272064plb.52.2023.07.03.06.25.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 03 Jul 2023 06:25:48 -0700 (PDT) Message-ID: <591e089a-6ccd-c5f3-4cd4-a332e2eae724@gmail.com> Date: Mon, 3 Jul 2023 20:25:35 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Content-Language: en-US To: =?UTF-8?Q?Mateusz_Jo=c5=84czyk?= , Alexandre Belloni , Carsten Hatger Cc: Linux Kernel Mailing List , Linux Regressions , x86@kernel.org From: Bagas Sanjaya Subject: Fwd: Read from RTC broken upon resume from suspend on HP Pro x360 435 G9 w/ AMD Ryzen 7 5825U Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I notice a regression report on Bugzilla [1]. Quoting from it: > Dear all, > > read access to the device's RTC fails upon resume from suspend with the following error message grabbed from the kernel ring buffer: > > [409610.163139] Unable to read current time from RTC > > The issue is rare and more likely to appear if the system has been in standby for more than 24hrs w/o interruption. > > Same issue is reported to appear on HP Elite G9 devices, cf. https://bbs.archlinux.org/viewtopic.php?id=283620 > > The issue screws up the systems time resulting in erroneous dated log entries, failing authentication, ..., thus requiring a reboot. > > Please see attached dmesg output (line 2069) for further information. > > AMD staff member suspected commit d2a632a8a11756197deb1341bbb09c09abaf20ce to cause a race condition, thus being responsible for the issue. They suggested to increase the delays introduced by latter commmit to 300us. Unfortunately this does not resolve the issue. > > Any help would be appreciated. See Bugzilla for the full thread and attached dmesg. Mateusz: It looks like this regression is caused by a commit of yours. Would you like to take a look on it? Anyway, I'm adding it to regzbot: #regzbot introduced: d2a632a8a11756 https://bugzilla.kernel.org/show_bug.cgi?id=217626 #regzbot title: reducing RTC_UIP polling period causes broken RTC on resume from suspend Thanks. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217626 -- An old man doll... just what I always wanted! - Clara