Red Hat Bugzilla – Bug 826191
upowerd spams logs with warning msg about /proc/timer_stats
Last modified: 2017-04-09 05:04:00 EDT
Description of problem:
The kernel we currently include in OLPC XO builds of F17 does not have /proc/timer_stats .
Kernel docs for /proc/timer_stats indicate it's a debugging/diagnostic tool http://www.kernel.org/doc/Documentation/timers/timer_stats.txt
It makes sense to issue a warning of timer_stats is not present. We currently get 6 warnings per second.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Build a kernel without timer_stats
2. Watch your logs
6 messages per second
1 warning message per powerd run
Author: Richard Hughes <email@example.com>
Date: Wed Oct 3 16:20:20 2012 +0100
Do not continue to poll if /proc/timer_stats is not readable
Ah, I see the fix is "upstream". ETA for landing in a release/build in Fedora?
(In reply to comment #3)
> Ah, I see the fix is "upstream". ETA for landing in a release/build in
If you can verify it fixes the bug, I'll do a new upstream release next week.
I am trying to verify this, but I ran into something very strange.
We found this issue in May, with F17 reasonably stable, while looking at other upower-related things. Between that and OLPC's OS release ("12.1.0") upower did not change, we did not add /proc/timer_stats and our upower config did not change either. Yet the behaviour seems to have vanished, or rather, I cannot repro it.
I spent a couple hours today trying to repro it on our final 12.1.0 with various configurations -- XO-1.5, XO-1.75, full battery, low battery, etc. I can probably go back to the exact build I used back in May and bisect it to which build it disappeared in, but that's very time-consuming.
Perhaps you can help me repro. Is this codepath conditional on something else?
(In reply to comment #5)
> Perhaps you can help me repro. Is this codepath conditional on something
Yes, hence why I was surprised by this bug. Try running something like gnome-power-statistics that uses the interface for stats reporting.
This issue is still present (or again). Might also be caused by https://bugs.freedesktop.org/show_bug.cgi?id=100626. Anyway, with upower-0.99.4-2.fc25.x86_64, I can reproduce these steps:
1. start gnome-power-manager
2. have a look at syslog
Syslog is spammed by the warning specified in https://cgit.freedesktop.org/upower/tree/src/up-wakeups.c#n467
What should happen:
Logging this once is enough.