Control: tags -1 - moreinfo On Sun, Feb 09, 2014 at 10:34:51PM -0500, Phillip Susi wrote: [...] > I'm not sure why this was reassigned from the kernel. Is this still > an issue today with a modern kernel?
This bug report sure has alot of posts in it so I think it's a good idea to post a summary (shining some light on the uncertanty about why this bug was reassigned). The reason this was reassigned from the kernel to util-linux is found in: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=277298#219 Basically, people where starting to give up on finding a solution in the kernel and where discussing a userspace workaround for broken rtc drivers. The bug should have been cloned and the clone reassigned (or a brand new bug report opened) instead, because the kernel bug was not solved (and who knows if it still is). At the same time, the bug should probably have been retitled to something like "Please implement workaround/timeout for broken rtc" and the severity lowered to wishlist. I'd argue that a good enough workaround already exists today, with the possibility of adding the --directisa switch in /etc/default/hwclock. I think this strikes a good balance between not hiding the bug while at the same time allowing a convenient way to work around the problem for users (who don't need to hack the init script). If it was up to me, I'd close this bug with the above explanation about /etc/default/hwclock. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
