Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Sleep tracer is not finding matching driver when performing an unlock #8205
We are not properly performing the driver lookup when we perform an unlock of the deep sleep counter. This only affects the stats counter and not the sleep counter itself, but it leads to confusing results when using the sleep tracer to monitor sleep.
This results in:
It still shows the timer holding a sleep lock when it has actually been released.
If we revert commit 9a0e879 then the problem goes away. We were doing a strcmp instead of a pointer compare in sleep_tracker_find():
Issue request type
[ ] Question