Re: [Mactel-linux-devel] Failed sensor reads

[Nicolas B. <ni...@bo...>]

Hello,

Even the Mac OS X driver seems to do strange things to try to "unstuck"
the device.

A proper way to fix the problem would be to fix the userspace
application to retry a few milliseconds later.

There are 2 ways to fix the problem in kernel too:
 - Store the values, ok, but what should we return if it's the first
time we read it? It would be relatively complicated, and would use some
kernel memory.
 - Wait and retry, but sometimes it can take a long time (I would say
something like up to a second to get a value), and we don't want to
block the application while it could do something better in the mean-time...

Best regards,

Nicolas

Sven Anders wrote:
> Hello Nicolas!
> 
> I'm using the GNOME sensors-applet and when it fails to read
> the values via libsensors due to a read error in the applesmc,
> the GUI flickers (because it's displaying ERROR instead of the
> value for some milliseconds).
> 
> In dmesg I have many of these (but I read before, these are harmless):
> 
> [29492.520000] applesmc: wait status failed: c != 58
> [29984.556000] applesmc: wait status failed: 5 != 54
> [29984.560000] applesmc: wait status failed: c != 5e
> 
> Now my question:
>  Is it possible to return the old sensors value when reading
>  the current one is not possible. This would eliminate my problem
>  and shouldn't be a problem for other programs. Maybe add a counter,
>  so if it countinues to fail, we can issue an error then.
> 
> Regards
>  Sven
>