#10827 NORM 1.75-so: RTC driver for 1.75
Zarro Boogs per Child
bugtracker at laptop.org
Mon Jun 13 21:12:31 EDT 2011
#10827: RTC driver for 1.75
---------------------------------+------------------------------------------
Reporter: cjb | Owner: saadia
Type: defect | Status: assigned
Priority: normal | Milestone: 1.75-software
Component: kernel | Version: not specified
Resolution: | Keywords:
Next_action: never set | Verified: 0
Deployment_affected: | Blockedby:
Blocking: 10893 |
---------------------------------+------------------------------------------
Comment(by Quozl):
Replying to [comment:6 saadia]:
> Downloaded os9, set RTC using hwclock --set --date . Confirmed time set
with hwclock. Rebooted, and time was Jan 1, 00:00. Rebooted again, repeat
setting time, reboot and back to 00:00 time.
Reproduced as described. The time is reset by the reboot. I presume
either the system reset or the firmware is the cause of the reset of the
time.
> Set time once more using hwclock, boot to OFW, examine time using select
/rtc, get-time. Time is correct.
Does not reproduce here. Tried several times. Time is incorrect; stack
after get-time shows 10 0 0 1 1 64, .clock shows 0100-01-01 00:00:16 UTC.
> Boot fully to Linux, and correct time is appearing now.
The different result you got is concerning. I wonder if it depends on
when the reboot happens in relation to the clock value. Can you tell me
how you rebooted to OFW? Or it might depend on when I test in relation to
UTC.
> There seems to be some kind of initial state after loading the os9 build
that is causing the clock to reset.
Yes, I agree. My gut feel is OpenFirmware startup.
I wonder it it might relate to #10989, where OpenFirmware doesn't seem to
get consistent results either.
--
Ticket URL: <http://dev.laptop.org/ticket/10827#comment:7>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list