Re: hwclock "hanging" for ~24 hours | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
Karel Zak schrieb: (...)
But would it solve the issue, really?Yes, that's core of the problem. But we also need to remove some return code checks from manipulate_clock(). These checks are unnecessary, because there is hclock_valid boolean... (this is my bug.)hwclock from busybox is able to show the clock (Tue Nov 30 00:00:00 1999 0.000000) and also set it; the above seems to exit only - and still, we're not able to show or set the clock?I'll send a patch ASAP.
Could you notify the list when the patch is ready, please? -- Tomasz Chmielewski http://wpkg.org -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Site Home] [Netdev] [Ethernet Bridging] [Linux Wireless] [Kernel Newbies] [Memory] [Security] [Linux for Hams] [Netfilter] [Bugtraq] [Rubini] [Photo] [Yosemite] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux Admin] [Samba] [Video 4 Linux] [Linux Resources]