Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 234125 - bettery/status and info files in /proc are extremely slow to access.
Summary: bettery/status and info files in /proc are extremely slow to access.
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 6
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-27 08:33 UTC by fernando.apesteguia
Modified: 2008-05-06 19:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:25:35 UTC

Attachments (Terms of Use)

Description fernando.apesteguia 2007-03-27 08:33:56 UTC
Description of problem:
The access to /proc/acpi/battery/BAT0/status and info files is extremely slow,
even 14 seconds to read the file (time cat info)

Version-Release number of selected component (if applicable):
Linux hammer 2.6.20-1.2925.fc6 #1 SMP Sat Mar 10 18:38:39 EST 2007 x86_64 x86_64
x86_64 GNU/Linux

How reproducible:

Steps to Reproduce: info or status files
Actual results:
The system takes too long to read the files (up to 14 seconds) without any workload

Expected results:
Response almost inmediate like with other files under /proc

Additional info:

Comment 1 Chuck Ebbert 2007-03-27 14:10:22 UTC
This is normal on some systems. Was it ever fast on any kernel version?

Comment 2 fernando.apesteguia 2007-03-29 08:55:38 UTC
Yes, it was always fast. I'm developing an application to show information from
/proc. I have never had this problem before with the same machine.

The battery of my machine seems to be fine: normal duration and normal charging

Comment 3 Bug Zapper 2008-04-04 06:41:38 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 4 Bug Zapper 2008-05-06 19:25:33 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.