Red Hat Bugzilla – Bug 215506
pci_set_power_state() in kernlog
Last modified: 2008-05-01 19:19:35 EDT
Description of problem:
The kernel prints the message
kernel: pci_set_power_state(): 0000:02:0a.0: state=3, current state=5
every several (7--8) seconds.
Version-Release number of selected component (if applicable):
100% for me
Steps to Reproduce:
1. Just boot the fc6 with the aforementioned kernel.
The kernel appears to operate quite ok, but wastes the kernlog with that message.
Probably that message should not be printed (at least not) so often.
Don't know if the following malfunctioning is dealt to those messages,
but it looks like it is:
gnome screen saver (or is it gnome power manager?) often fails to start
and to put screen in powersaveing mode, instead it crashes the session
(while gconfd states that that is normal session termination).
can you lspci and find out which device maps to 0000:02:0a.0 ?
do the messages only relate to that device ?
lspci -v -s 0000:02:0a.0
02:0a.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
Flags: bus master, medium devsel, latency 64, IRQ 5
I/O ports at d800 [size=64]
[virtual] Expansion ROM at efe20000 [disabled] [size=64K]
Have forgotten to answer the second question:
yes the messages are always the same, i.e. they do relate that device only.
The messages are only printed to kernlog when a user is logged in X session
(actually gnome session, can say nothing about kde).
Killing gnome-power-manager doesn't stop the messages.
I put a probe in pci_set_power_state() and obtained this stack dump:
pci_set_power_state(): 0000:00:0b.0: state=3, current state=5
[<f88c1089>] jpci_set_power_state+0x1a/0x25 [jprobe_powerstate]
[<f8a95816>] vortex_ioctl+0xd8/0x15d [3c59x]
does it help ?
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
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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping 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 http://fedoraproject.org/wiki/BugZappers
> We strongly encourage you to upgrade to a current Fedora release.
To my regret I cannot upgrade to a later Fedora release
as since Fedora 7 PATA disks are always treated as SCSI disks
and SCSI disks cannot contain more than 15 partitions,
while I do have more than twenty of them.
It seems I should have to switch to some other Linux distribution.
Thank you for your update