From: Hugh Dickins <hughd@google.com>
To: Saravana Kannan <saravanak@google.com>
Cc: Hugh Dickins <hughd@google.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Thierry Reding <treding@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vincent Huang <vincent.huang@tw.synaptics.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Andrew Duggan <aduggan@synaptics.com>,
Lucas Stach <l.stach@pengutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: 5.11-rc device reordering breaks ThinkPad rmi4 suspend
Date: Mon, 11 Jan 2021 20:42:54 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.11.2101112026570.3885@eggly.anvils> (raw)
In-Reply-To: <CAGETcx8mNW=skm-2W6tS20wG1BxJW6ROMqDaktN5udKTeZtNrQ@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2196 bytes --]
On Mon, 11 Jan 2021, Saravana Kannan wrote:
> On Mon, Jan 11, 2021 at 4:44 PM Hugh Dickins <hughd@google.com> wrote:
> > On Mon, 11 Jan 2021, Saravana Kannan wrote:
> > >
> > > Did you see this patch change the organization of devices under /sys/devices/?
> > > The rmi* devices need to be under one of the i2c devices after this
> > > patch. Is that not the case? Or is that the case, but you are still
> > > seeing suspend/resume issues?
> >
> > Now that I look, yes, that patch has moved the directory
> > /sys/devices/rmi4-00
> > to
> > /sys/devices/pci0000:00/0000:00:1f.4/i2c-6/6-002c/rmi4-00
>
> What about child devices of rmi4-00? Does it still have the
> rmi4-00.fn* devices as children? I'd think so, but just double
> checking.
Yes, the patch moved the rmi4-00 directory and its contents.
>
> >
> > But I still see the same suspend issues despite that.
>
> Can you please get new logs to see if the failure reasons are still
> the same? I'd think this parent/child relationship would at least
> avoid the "Failed to read irqs" errors that seem to be due to I2C
> dependency.
No, it did not avoid the "Failed to read irqs" error (though my
recollection from earlier failures before I mailed out, is that
that particular error is intermittent: sometimes it showed up,
other times not; but always the "Failed to write sleep mode").
I configured CONFIG_PM_DEBUG=y and booted with pm_debug_messages
this time, dmesgsys.tar attached, contents:
dmesg.rc3 # dmesg of boot and attempt to suspend on 5.11-rc3
sys.rc3 # find /sys | sort | grep -v /sys/fs/cgroup afterwards
dmesg.saravana # dmesg of boot and attempt to suspend with your patch
sys.saravana # find /sys | sort | grep -v /sys/fs/cgroup afterwards
dmesg.revert # dmesg of boot+suspend+resume, rc3 without 5b6164d3465f
sys.revert # find /sys | sort | grep -v /sys/fs/cgroup afterwards
Not as many debug messages as I was expecting: perhaps you can point
me to something else to tune to get more info out? And perhaps it was
a mistake to snapshot the /sys hierarchy after rather than before:
I see now that it does make some difference. I filtered out
/sys/fs/cgroup because that enlarged the diffs with no relevance.
Hugh
[-- Attachment #2: Type: APPLICATION/x-tar, Size: 99912 bytes --]
next prev parent reply other threads:[~2021-01-12 4:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 4:44 Hugh Dickins
2021-01-11 12:57 ` Rafael J. Wysocki
2021-01-11 17:20 ` Hugh Dickins
2021-01-11 13:43 ` Thierry Reding
2021-01-11 14:43 ` Rafael J. Wysocki
2021-01-11 14:57 ` Rafael J. Wysocki
2021-01-11 16:12 ` Thierry Reding
2021-01-11 16:57 ` Rafael J. Wysocki
2021-01-11 22:44 ` Saravana Kannan
2021-01-11 23:42 ` Hugh Dickins
2021-01-12 0:14 ` Saravana Kannan
2021-01-12 0:44 ` Hugh Dickins
2021-01-12 2:16 ` Saravana Kannan
2021-01-12 4:42 ` Hugh Dickins [this message]
2021-01-12 12:43 ` Rafael J. Wysocki
2021-01-12 17:37 ` Thierry Reding
2021-01-12 17:57 ` Thierry Reding
2021-01-12 20:38 ` Saravana Kannan
2021-01-11 17:42 ` Hugh Dickins
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=alpine.LSU.2.11.2101112026570.3885@eggly.anvils \
--to=hughd@google.com \
--cc=Jason@zx2c4.com \
--cc=aduggan@synaptics.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--cc=treding@nvidia.com \
--cc=vincent.huang@tw.synaptics.com \
/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
all inboxes | Powered by JetHome®