|
Bugzilla – Full Text Bug Listing |
| Summary: | kernel sets hardware clock to random past dates during boot on Pegasos | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | peter czanik <peter> |
| Component: | Kernel | Assignee: | Olaf Hering <ohering> |
| Status: | RESOLVED WORKSFORME | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | PowerPC | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | output of kernel update | ||
|
Description
peter czanik
2006-02-18 03:03:33 UTC
Olaf? could be related to bug #149895, fix is work in progress. http://lkml.org/lkml/2006/2/15/5 Can you test the kernel of the day tomorrow? ftp://ftp.suse.com/pub/projects/kernel/kotd/ppc/HEAD/ timestamp needs to be at least 20060220092013 Created attachment 69482 [details]
output of kernel update
There are some strange messages from a perl module at the end of the log. Probably due that there is no boot manager installed on Pegasos (might change with GRUB2 in the future...).
I did about 30 reboots this morning with kernel-default-2.6.16_rc4-20060220183514.ppc.rpm The situation improved a lot, but still not perfect. When I boot this KOTD kernel over and over again, there are no more random time changes to the past, as it was the case before. When I boot this KOTD kernel after the 10.0 kernel, the time change is no more random, but always back to 1970. If I boot the 10.0 kernel over and over again, time remains correct between the reboots, just as before. Booting 10.0 after the 10.1 KOTD kernel shows correct time also. One more note: booting Gentoo with 2.6.15 after this KOTD has correct date, and booting this KOTD after the above mentioned Gentoo kernel also shows proper date. is that still broken? can you try 2.6.16-rc6? there was a related patch, maybe it fixes also this bug. Tested with KOTD, the bug is still there, the same way as in comment #5. I dont see it here, btw. do you know when it started? I noticed it some time in January, I don't recall when exactly. I also had a real battery problem for forgetting date, that's why I did not report it earlier. can you try a selfcompiled 2.6.15.X and see if its aleady broken there? Does a gentoo kernel count as self compiled? It's a 2.6.15 with gentoo patches and compiled by me. Did a good number of reboots, and here are the results: - gentoo->suse10.1: correct date - suse10.0->suse10.1: wrong date - suse10.0->gentoo: correct date, but booting 10.1 thereafter it's 1970 again. In summary: if I ever boot 10.0, 10.1 will go back to 1970. hmm, can you do a chmod a-x /sbin/hwclock on all these installations? just to check if its the kernel or if some app sets the wrong date. Checked it: dates remain correct. Status? Peter, does this still happen? I guess it does. Yes, it still happens. I think, it's a problem with 10.0 hwclock, as I have not seen it with any other distributions, or any later SUSE versions. lets not bother about this anymore. |