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 1B7B8C001E0 for ; Thu, 27 Jul 2023 12:26:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233487AbjG0M0g (ORCPT ); Thu, 27 Jul 2023 08:26:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59912 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233914AbjG0M0U (ORCPT ); Thu, 27 Jul 2023 08:26:20 -0400 Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 778893A8F; Thu, 27 Jul 2023 05:25:33 -0700 (PDT) Received: by mail-pl1-x62e.google.com with SMTP id d9443c01a7336-1b8c81e36c0so5455045ad.0; Thu, 27 Jul 2023 05:25:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690460721; x=1691065521; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=Q8w2BroilchUm0vlMoQZCfmeRkJCD+OaWa9ouggpUhE=; b=sUKo94Y7jEq4Of0ShNppcptl1bCqlql1WxhA77SDF4oX/ZTgGKfLfWXCaCclk5ezgF IwIjH2S43Zy/sx5UZtoNF5iKjTSYX8odQPEUystkwgkmBpEldUzi60HBj+/pBrvNg8dV Zm7KtORoej/Wgbexc9OE94Yo6fQQ1SCpL917giXDnCUVAywLCSczBhck4vxfCmwvdmJ0 9UbEpmc3yaqkt5ZXzTu284KAd+rqgr2FZiwlpReZZBTVuv0OEQaZXcyvmZwf2K4yTgiy jfLFYZV4ciInNJuuHChpim0q45kwQNMJERFpjmYcP5WfkqyH4K43oQsFebb9TMPJo8Gc +v6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690460721; x=1691065521; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Q8w2BroilchUm0vlMoQZCfmeRkJCD+OaWa9ouggpUhE=; b=Z1NgnnBVPrpTTGY5oJDbUGGExxzsOdUH8zYld+oF6qfqn5jp1/HiEaoM9PqiJRK0P8 JLP637TNO+T1gN/Wn68BYqWnBUHLrk9HCWRS01ik7KwqLHxf8HpMMuH4suj9op7Bwel4 Lxu+4CsPN8x2tTmBR/y+LPOh1dvpmt9M7j0kipmnK3rrvxOxqBcDgFnwrUtHZbZm0JO4 IQMIqYqDPKw/WrmhejfsPhoosPWMnp6juGi+fBydlUaiJafBfKiBIwC0yoD21wXrYZhu XLs53D0KiZassdta/xMHBC/J7kAKq9XdWguTcr0iciQhRRVq0+Akp/Vo8iBz1xAK7o9o ix4g== X-Gm-Message-State: ABy/qLbnx7KzhUBw5Cnm6c71PH1WU/QBSgFaaS9AvwJBetX1OLtFwoiR PiXD/XIw0yJ1CWy8t6SPkMI= X-Google-Smtp-Source: APBJJlGnPll1D6uCbmYaFm6LhePlGO8cMGwnGGxYven5jT/I5hlWh+/MuAkBl8Oubp5VfczdMLBttA== X-Received: by 2002:a17:903:182:b0:1bb:e74b:39ff with SMTP id z2-20020a170903018200b001bbe74b39ffmr148542plg.0.1690460721291; Thu, 27 Jul 2023 05:25:21 -0700 (PDT) Received: from [192.168.1.121] ([65.129.146.152]) by smtp.gmail.com with ESMTPSA id e16-20020a17090301d000b001bb381b8260sm1503595plh.100.2023.07.27.05.25.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Jul 2023 05:25:20 -0700 (PDT) Message-ID: Date: Thu, 27 Jul 2023 06:25:19 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: Scsi_bus_resume+0x0/0x90 returns -5 when resuming from s3 sleep To: Damien Le Moal , Thorsten Leemhuis Cc: regressions@lists.linux.dev, Mario Limonciello , Bart Van Assche , LKML , stable@vger.kernel.org References: <0e272abe-292d-d58f-cf80-55868e793abc@gmail.com> <6b66dd9a-8bd5-2882-9168-8e6e0848c454@leemhuis.info> <86435987-734e-c6c1-a857-1ba80da709fe@gmail.com> <48bc1736-5e4e-3a9b-3715-60509c333bb1@kernel.org> Content-Language: en-US From: TW In-Reply-To: <48bc1736-5e4e-3a9b-3715-60509c333bb1@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org It was all 1 patch but the first change had a formatting issue from the email format I guess. So I fixed that and the patch went through and looks like the drive error message has stopped. Still a little slow coming back but that error is gone at least. Jul 27 05:05:05 rageworks systemd[1]: Starting System Suspend... Jul 27 05:05:05 rageworks systemd-sleep[1624]: Entering sleep state 'suspend'... Jul 27 05:05:05 rageworks kernel: PM: suspend entry (deep) Jul 27 05:05:05 rageworks kernel: Filesystems sync: 0.246 seconds Jul 27 05:05:26 rageworks kernel: Freezing user space processes Jul 27 05:05:26 rageworks kernel: Freezing user space processes completed (elapsed 0.001 seconds) Jul 27 05:05:26 rageworks kernel: OOM killer disabled. Jul 27 05:05:26 rageworks kernel: Freezing remaining freezable tasks Jul 27 05:05:26 rageworks kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds) Jul 27 05:05:26 rageworks kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jul 27 05:05:26 rageworks kernel: serial 00:05: disabled Jul 27 05:05:26 rageworks kernel: sd 9:0:0:0: [sdc] Synchronizing SCSI cache Jul 27 05:05:26 rageworks kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache Jul 27 05:05:26 rageworks kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Jul 27 05:05:26 rageworks kernel: sd 9:0:0:0: [sdc] Stopping disk Jul 27 05:05:26 rageworks kernel: sd 1:0:0:0: [sdb] Stopping disk Jul 27 05:05:26 rageworks kernel: sd 0:0:0:0: [sda] Stopping disk Jul 27 05:05:26 rageworks kernel: ACPI: PM: Preparing to enter system sleep state S3 Jul 27 05:05:26 rageworks kernel: ACPI: PM: Saving platform NVS memory Jul 27 05:05:26 rageworks kernel: Disabling non-boot CPUs ... Jul 27 05:05:26 rageworks kernel: smpboot: CPU 1 is now offline Jul 27 05:05:26 rageworks kernel: smpboot: CPU 2 is now offline Jul 27 05:05:26 rageworks kernel: smpboot: CPU 3 is now offline Jul 27 05:05:26 rageworks kernel: ACPI: PM: Low-level resume complete Jul 27 05:05:26 rageworks kernel: ACPI: PM: Restoring platform NVS memory Jul 27 05:05:26 rageworks kernel: Enabling non-boot CPUs ... Jul 27 05:05:26 rageworks kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1 Jul 27 05:05:26 rageworks kernel: CPU1 is up Jul 27 05:05:26 rageworks kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2 Jul 27 05:05:26 rageworks kernel: CPU2 is up Jul 27 05:05:26 rageworks kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3 Jul 27 05:05:26 rageworks kernel: CPU3 is up Jul 27 05:05:26 rageworks kernel: ACPI: PM: Waking up from system sleep state S3 Jul 27 05:05:26 rageworks kernel: xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit Jul 27 05:05:26 rageworks kernel: usb usb1: root hub lost power or was reset Jul 27 05:05:26 rageworks kernel: usb usb2: root hub lost power or was reset Jul 27 05:05:26 rageworks kernel: sd 0:0:0:0: [sda] Starting disk Jul 27 05:05:26 rageworks kernel: sd 1:0:0:0: [sdb] Starting disk Jul 27 05:05:26 rageworks kernel: sd 9:0:0:0: [sdc] Starting disk Jul 27 05:05:26 rageworks kernel: serial 00:05: activated Jul 27 05:05:26 rageworks kernel: ata6: SATA link down (SStatus 0 SControl 330) Jul 27 05:05:26 rageworks kernel: ata5: SATA link down (SStatus 0 SControl 330) Jul 27 05:05:26 rageworks kernel: ata9: SATA link down (SStatus 0 SControl 300) Jul 27 05:05:26 rageworks kernel: usb 1-10: reset full-speed USB device number 4 using xhci_hcd Jul 27 05:05:26 rageworks kernel: usb 1-8: reset full-speed USB device number 3 using xhci_hcd Jul 27 05:05:26 rageworks kernel: usb 1-7: reset full-speed USB device number 2 using xhci_hcd Jul 27 05:05:26 rageworks kernel: OOM killer enabled. Jul 27 05:05:26 rageworks kernel: Restarting tasks ... done. Jul 27 05:05:26 rageworks kernel: random: crng reseeded on system resumption Jul 27 05:05:26 rageworks kernel: PM: suspend exit On 7/27/23 04:27, Damien Le Moal wrote: > On 7/27/23 19:22, TW wrote: >> I managed to fix the patch file, guess the formatting messed up a bit. So will >> try with those patches installed. > Just in case, patch fil attached to avoid formatting issues. > >