From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: linux-omap@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: SDP4430 nightly regression (was: Re: [GIT PULL] two omap regression fixes)
Date: Fri, 3 Nov 2017 10:26:48 -0700 [thread overview]
Message-ID: <20171103172648.GI28152@atomide.com> (raw)
In-Reply-To: <20171103160518.GG28152@atomide.com>
* Tony Lindgren <tony@atomide.com> [171103 16:07]:
> * Russell King - ARM Linux <linux@armlinux.org.uk> [171103 10:45]:
> > In the diffstat between the two build trees (post merge), I don't see
> > anything in arch/arm that could account for it. I do see some power
> > changes:
> >
> > drivers/base/power/domain_governor.c | 53 +--
> > drivers/base/power/qos.c | 2 +-
> > drivers/base/power/runtime.c | 2 +-
> > drivers/base/power/sysfs.c | 25 +-
> >
> > but nothing in tty or serial. These power changes look like QoS
> > changes, which probably aren't related.
> >
> > Just to make sure, I've diffed the build tree SHAs and the change in
> > Linus' tip, and the two diffs match apart from a couple of SHA blob
> > hashes on a couple of files (EFI stub and MAINTAINERS).
>
> Initiating git bisect sequence.
Seems this is now fixed in the mainline kernel. I also confirmed
that v4.14-rc6 fails to resume. Most likely Rafael's revert of
the following two commits fixed the issue:
5ba257249e9c ("Revert "PM / QoS: Fix default runtime_pm device resume latency"")
d5919dcc349d ("Revert "PM / QoS: Fix device resume latency PM QoS"")
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: SDP4430 nightly regression (was: Re: [GIT PULL] two omap regression fixes)
Date: Fri, 3 Nov 2017 10:26:48 -0700 [thread overview]
Message-ID: <20171103172648.GI28152@atomide.com> (raw)
In-Reply-To: <20171103160518.GG28152@atomide.com>
* Tony Lindgren <tony@atomide.com> [171103 16:07]:
> * Russell King - ARM Linux <linux@armlinux.org.uk> [171103 10:45]:
> > In the diffstat between the two build trees (post merge), I don't see
> > anything in arch/arm that could account for it. I do see some power
> > changes:
> >
> > drivers/base/power/domain_governor.c | 53 +--
> > drivers/base/power/qos.c | 2 +-
> > drivers/base/power/runtime.c | 2 +-
> > drivers/base/power/sysfs.c | 25 +-
> >
> > but nothing in tty or serial. These power changes look like QoS
> > changes, which probably aren't related.
> >
> > Just to make sure, I've diffed the build tree SHAs and the change in
> > Linus' tip, and the two diffs match apart from a couple of SHA blob
> > hashes on a couple of files (EFI stub and MAINTAINERS).
>
> Initiating git bisect sequence.
Seems this is now fixed in the mainline kernel. I also confirmed
that v4.14-rc6 fails to resume. Most likely Rafael's revert of
the following two commits fixed the issue:
5ba257249e9c ("Revert "PM / QoS: Fix default runtime_pm device resume latency"")
d5919dcc349d ("Revert "PM / QoS: Fix device resume latency PM QoS"")
Regards,
Tony
next prev parent reply other threads:[~2017-11-03 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 19:55 [GIT PULL] two omap regression fixes Tony Lindgren
2017-11-02 19:55 ` Tony Lindgren
2017-11-03 10:43 ` SDP4430 nightly regression (was: Re: [GIT PULL] two omap regression fixes) Russell King - ARM Linux
2017-11-03 10:43 ` Russell King - ARM Linux
2017-11-03 16:05 ` Tony Lindgren
2017-11-03 16:05 ` Tony Lindgren
2017-11-03 17:26 ` Tony Lindgren [this message]
2017-11-03 17:26 ` Tony Lindgren
2017-11-03 17:44 ` Russell King - ARM Linux
2017-11-03 17:44 ` Russell King - ARM Linux
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=20171103172648.GI28152@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.