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 1A53DCDB47E for ; Thu, 12 Oct 2023 23:57:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233798AbjJLX5o (ORCPT ); Thu, 12 Oct 2023 19:57:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54126 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233273AbjJLX5m (ORCPT ); Thu, 12 Oct 2023 19:57:42 -0400 Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 990D8C0; Thu, 12 Oct 2023 16:57:40 -0700 (PDT) Received: by mail-pf1-x431.google.com with SMTP id d2e1a72fcca58-692a885f129so1266100b3a.0; Thu, 12 Oct 2023 16:57:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697155060; x=1697759860; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:from:subject:user-agent:mime-version:date:message-id:from:to :cc:subject:date:message-id:reply-to; bh=IMk7ef3z6b35hTlTRh2H+b/l6njrMDplSZDZc4/1mAU=; b=Es9zu6N1QSqtN0wWh6wcdjSs6t5r607Dpekx+F9OOHCU+KEPbDlPl05S2R7eH44GBJ FluZwcsDmGjBEVJsNV0uNOC4RWC1XBjUK44ibPRqC4ZAyypx5UPZo10aGy9VTYO0l+jU GF4ZKKva51YGoLSUsCAm2E0xIVgDuque+PZz1OScRqCXvrrnlkoqSZY1UocoLZfLy/cU aQQX4zjQEPz42lJhHTGbbpacpakkAVvrTXfs972mt6MNbLqbtcjjajqy2tvhu7VmRttu NiQTt9vZ4nZMtumB+lGjh7Ng9EXdD9+X5Z5dlqz0gvsJhDKb10T2HIV63k0ueQclXo6f hY/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697155060; x=1697759860; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:from:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=IMk7ef3z6b35hTlTRh2H+b/l6njrMDplSZDZc4/1mAU=; b=GfjEl/NTOg564u17I4ZEMHzmWbo5RPlx6LRbTNFup/vpH1o5kN0fwe9XP7nuTqEbP8 AjdvgAgZUAMxkBPQ0OrWhr452Py++k6EHWa8EvkvKEDiJoe+erY5Invv7CvQ3i98qfI0 EbsxUOxZjklYhpuvuh+qmV93FgR5v3kRNjeVDcgYv/QZlQ4FmWEvRneiPpFs2ZN2hEXl XyICH7roUT6Fx/q22IXPJdQm/F1wEg5lccWE+syfJkzhl8c/E9zjXtnLULRfzdVmco04 +gOsEOVsGti5AzmJlDd06ji8KO3tk+0loeDBZ8gFf2yhBnIWlNgPqAH4wJcMtcTGRT3L HpTA== X-Gm-Message-State: AOJu0Yy76fl8WdcrieiadlqILyi/ToqS2/7sbsPedxR54/omi8FpFPEh AxrVrsUNIv+/+tBxyNbJfZGA8YZm93o= X-Google-Smtp-Source: AGHT+IGXYpN9ClsEETOLPh4A+17Ca/iEmHa91MMqRHzbAa627nCzyd9VHmCdfnui/FFLZ8NActc9kg== X-Received: by 2002:a05:6a21:1f16:b0:152:1ce8:ce3a with SMTP id ry22-20020a056a211f1600b001521ce8ce3amr20185803pzb.18.1697155059665; Thu, 12 Oct 2023 16:57:39 -0700 (PDT) Received: from [192.168.0.106] ([103.131.18.64]) by smtp.gmail.com with ESMTPSA id q2-20020a170902edc200b001b7f40a8959sm2553077plk.76.2023.10.12.16.57.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 12 Oct 2023 16:57:38 -0700 (PDT) Message-ID: Date: Fri, 13 Oct 2023 06:57:33 +0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Fwd: Intel 7560 LTE Modem stops working after resuming from standby From: Bagas Sanjaya To: Linux Kernel Mailing List , Linux Regressions , Linux Networking , Linux Intel Wireless WAN Cc: M Chetan Kumar , "David S. Miller" , Loic Poulain , Sergey Ryazanov , Johannes Berg References: <267abf02-4b60-4a2e-92cd-709e3da6f7d3@gmail.com> Content-Language: en-US In-Reply-To: <267abf02-4b60-4a2e-92cd-709e3da6f7d3@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/10/2023 16:52, Bagas Sanjaya wrote: > Hi, > > I notice a regression report on Bugzilla [1]. Quoting from it: > >> I noticed a few days ago, after Fedora moved to Kernel 6.5, that my Intel LTE Modem was not working anymore after resuming from standby. >> >> The journal listed this error message multiple times: >> kernel: iosm 0000:01:00.0: msg timeout >> >> It took me a while to determine the root cause of the problem, since the modem did not work either in the following warm reboots. >> Only a shutdown revived the modem. >> >> I did a bisection of the error and I was able to find the culprit: >> >> [e4f5073d53be6cec0c654fac98372047efb66947] net: wwan: iosm: enable runtime pm support for 7560 > > See Bugzilla for the full thread. > > Anyway, I'm adding this regression to regzbot: > > #regzbot introduced: e4f5073d53be6c https://bugzilla.kernel.org/show_bug.cgi?id=217996 > #regzbot title: pm support for Intel 7560 makes the modem stops working after resume > FYI, the reporter had uploaded full dmesg output on Bugzilla. Also, he noted shutdown abnormality: > also I should mention, that if this error occurs, I am unable to shutdown my system anymore. "poweroff" does not turn the laptop off, it simply triggers a reboot, where the modem is still not functional. Only pressing the powerbutton >4 secs "resets" the device. Thanks. -- An old man doll... just what I always wanted! - Clara