On Wed, 2010-02-03 at 03:42 +0100, Benjamin Cama wrote: > Le mercredi 03 février 2010 à 02:02 +0000, Ben Hutchings a écrit : > > Error 22 is EINVAL and actually indicates an invalid time. > > OK. I actually wanted to solve this bug to also help a bug somewhat > related to #535354, which prevent hwclock to write the hardware clock. > > Actually, hwclock first read the hardware clock before writing to it, > and stops if reading fails, which causes my problem (yes, i know, not > this bug). > > > If you don't mind applying another patch, this would help debug this > > further: > > No problem. But by just reading it, I felt the problem : an invalid date > is stored in the RTC. > > What's in my logs (I may have missed the SMU stuff as it seems "make" > didn't feel like recompiling it): Only one of CUDA, PMU or SMU will be used but since I have no idea which machines use which I covered all of them in the patch. > [ 20.172405] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0 > [ 20.186144] pmu_get_time: now = 2454713 This is supposed to be a count of seconds since 1904-01-01, so it is indeed invalid. [...] > But still, it would be usefull to be able to set the RTC for those with > still a bit of juice in their battery. So, this is not this bug but > another one (related to hwclock), if you agree with my analysis. I'll > fill another one soon, if so. Right, the bug is in hwclock. Ben. -- Ben Hutchings I'm not a reverse psychological virus. Please don't copy me into your sig.
Attachment:
signature.asc
Description: This is a digitally signed message part