Hey Rafael,
On Fri, 2017-01-27 at 00:07 +0100, Rafael J. Wysocki wrote:
On Thu, Jan 26, 2017 at 4:15 PM, Bastien Nocera [off-list ref]
wrote:
quoted
On Fri, 2017-01-20 at 16:52 +0100, Bastien Nocera wrote:
quoted
Hey,
TLDR:
# first bad commit: [50ba22479c324c0d9dc8134d519dcba92d83a8a7]
Merge
back earlier ACPI PM material for v4.3.
hid-sensor-hub devices only start sending events through the IIO
trigger after a suspend/resume cycle.
Other IIO drivers don't seem to exhibit those problems.
I had another go, trying to break into the merge commit, and it's
slightly more precise, but still doesn't make any sense to me.
# first bad commit: [3431e490b50356b56084305a2e93b3a980802b22]
Merge
branch 'acpi-scan' into acpi-pm
Any ideas? I'm running out of them...
The parents of this merge are 5af310a8ee70 and 1dcc3d3362b0.
Can you please check if the problem is present in any of them alone?
Both of those were already in the git bisect output:
# good: [5af310a8ee70dd6a588c8ee1d4487a230a7b7b65] Merge tag 'ib-mfd-base-acpi-dma-v4.3' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd into acpi-pm
git bisect good 5af310a8ee70dd6a588c8ee1d4487a230a7b7b65
# good: [1dcc3d3362b0c97e48290f7786be85b4cec2a147] ACPI / bus: Move ACPI bus type registration
git bisect good 1dcc3d3362b0c97e48290f7786be85b4cec2a147
Or did I do this wrong?
If not, it is theoretically possible that the merge itself had
introduced it (as this is not a trivial merge).
Yeah, I tried diving into the merge, but never managed to do so.
Cheers