pci_set_device_state error

[Dazed_75]

On Thu, Jul 8, 2010 at 5:57 AM, Eric Shubert <ejs at shubes.net> wrote:

> Dazed_75 wrote:
>
>>
>> <timestamp> kernel: [nnnn.nnnnnn] phy0 -> rt2500 pci_set_device_state:
>> Error - Device failed to enter state 1 (-16).
>>
>
>  2) How does one interpret the [nnnn.nnnnnn] found in so many logs?  I
>> always assumed it was seconds and microseconds since some event, but ...
>>
>
> It appears to be set to zero when the kernel boots, but the integer portion
> sometimes increases faster than seconds, and sometimes slower.
> BL, I don't really know (so what else is new?). Did you google it?
>
> --
> -Eric 'shubes'
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>

Yes, I did.  Google found no results whatsoever even for just the
"pci_set_device_state".  I am guessing that is the name of a function/class
in the driver or a library it uses but I don't know.  I was hoping the
source, a header, or some documentation for it might have been found by
Google.  Then I Googled "rt2500" but getting the current source would
require me to set up and configure git.  So I downloaded the older source
and extracted it to a temp directory.  Once there doing a grep pci * only
resulted in "rt_config.h:#include <linux/pci.h>".  So then I Googled
linux/pci.h and found a version of that file which does not contain the
"pci_set_device_state".  At that point I confess it being beyond me.

-- 
Dazed_75 a.k.a. Larry

The spirit of resistance to government is so valuable on certain occasions,
that I wish it always to be kept alive.
 - Thomas Jefferson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.PLUG.phoenix.az.us/pipermail/plug-discuss/attachments/20100708/8ccb6778/attachment.html>