From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Input <linux-input@vger.kernel.org>,
Linux i2c Devices <linux-i2c@vger.kernel.org>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Wolfram Sang <wsa@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
kolAflash@kolahilft.de
Subject: Fwd: ThinkPad L540: suspend not working (deep / S3 / standby, regression Linux 4.19 -> 6.1)
Date: Fri, 19 May 2023 20:19:39 +0700 [thread overview]
Message-ID: <73883c7d-42db-7ac6-fa43-b9be45cdc795@gmail.com> (raw)
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> ThinkPad L540 failed suspend deep dmesg output - Linux-6.1.27 from Debian-12
>
> Since updating from Linux-4.19 to Linux-6.1.27 suspend deep is not working anymore.
> (a.k.a. S3, standby or suspend to ram)
>
> Notebook: ThinkPad L540 20AU-S00N00
> OS: Debian-12 "Bookworm" (was Debian-10 "Buster" before)
> Kernel: Linux-6.1.27 from Debian-12 (was Linux-4.19 from Debian-10 before)
>
> Can I provide any other helpful information?
> Do you need a test with a vanilla Linux-6.1 kernel?
> Should I perform any other tests or maybe try out boot parameters?
>
> Full dmesg output attached.
> Excerpt:
> rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
> rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
> rmi4_physical rmi4-00: Failed to suspend functions: -6
> rmi4_smbus 0-002c: Failed to suspend device: -6
> rmi4_smbus 0-002c: PM: dpm_run_callback(): rmi_smb_suspend+0x0/0x40 [rmi_smbus] returns -6
> rmi4_smbus 0-002c: PM: failed to suspend async: error -6
> sd 4:0:0:0: [sda] Synchronizing SCSI cache
> sd 4:0:0:0: [sda] Stopping disk
> PM: Some devices failed to suspend, or early wake event detected
> sd 4:0:0:0: [sda] Starting disk
> OOM killer enabled.
> Restarting tasks ...
> rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts!
> psmouse: probe of serio2 failed with error -1
>
>
>
> Maybe related:
>
> 5.17-rc regression: X1 Carbon touchpad not resumed
> https://lore.kernel.org/lkml/YgF%2F0QGFN4SppLKg@shikoro/T/
FYI, I guess the regression is also introduced by 172d931910e1db
("i2c: enable async suspend/resume on i2c client devices") and
should have been fixed by 7b1f781f2d2460 ("Input: psmouse - set up
dependency between PS/2 and SMBus companions"), but it doesn't
fix the reporter's issue.
Anyway, I'm adding this to regzbot:
#regzbot introduced: v4.19..v6.1 https://bugzilla.kernel.org/show_bug.cgi?id=217462
#regzbot title: psmouse suspend failed on ThinkPad L540
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217462
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-05-19 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 13:19 Bagas Sanjaya [this message]
2023-05-19 13:46 ` Fwd: ThinkPad L540: suspend not working (deep / S3 / standby, regression Linux 4.19 -> 6.1) Hans de Goede
2023-05-19 13:56 ` Bagas Sanjaya
2023-05-20 2:16 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=73883c7d-42db-7ac6-fa43-b9be45cdc795@gmail.com \
--to=bagasdotme@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=kolAflash@kolahilft.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=wsa@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).