Ticket #700 (closed defect: fixed)
Time/Date stops in suspend
| Reported by: | reddog@… | Owned by: | jserv@… |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | openmoko-panel-clock | Version: | 2007.2 |
| Severity: | normal | Keywords: | |
| Cc: | buglog@…, miles_hsieh@…, phil.openmoko@… | Blocked By: | |
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | PatchReviewResult: | ||
| Reproducible: |
Description
I set the correct date/time with "date" and save this with hwclock --systohc.
Then i bring Neo to suspend and after 10 minutes the system time is 10 minutes
back. HW-Clock is korrekt.
The Build is latest svn 2007.2 from 10. Aug 2007.
Change History
comment:6 Changed 6 years ago by miles_hsieh@…
I set the correct time with "date" and save this with "hwclock -w".
After a successful suspend/resume cycle, the system time is still almost the
same as the hardware
clock.
In a successful suspend/resume cycle, I try four times to get the same result.
It seems that the system time is fine.
comment:7 Changed 6 years ago by phil.openmoko@…
I see this issue with OM2007.2 / kernel 2.6.21.6-moko11-r2 (Snapshot 20070825) +
ipkg updates to Aug 30th on my Neo at the moment.
I'll try the latest build snapshot (20070831) + ipkg updates.
Note: See
TracTickets for help on using
tickets.
This sounds like the hardware RTC is not read out during resume.
I am afraid without further investigation I also don't know how this is supposed
to happen during regular suspend/resume of linux systems.
Jserv: Can you assign this task to somebody in your team, please?