system clock not adjusted when hardware clock in localtime

This bug was fixed in the package util-linux - 2.16-1ubuntu4

---------------
util-linux (2.16-1ubuntu4) karmic; urgency=low

  * Removed access checks for hardware clock when called with --systz,
    since we may not have the rtc device at the point we run hwclock.
    I believe this is the cause of LP: #436076.
  * Set kernel timezone even when the hardware clock is in UTC.
    LP: #426886.

  * Don't step the system clock, or save the hardware clock on upgrades
    in case the time isn't quite correct. LP: #430878.
  * Remove the hwclock.sh and hwclockfirst.sh scripts on upgrades, since
    these are now Upstart jobs. LP: #434767.

 -- Scott James Remnant <email address hidden> Thu, 24 Sep 2009 12:31:29 -0700

since upgrading to karmic (release), I get the following very often:

 /dev/sda1: Superblock last mount time (Thu Sep 24 20:58:00 2009,
          now = Thu Sep 24 19:59:23 2009) is in the future.

  /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
          (i.e., without -a or -p options)
  mountall: fsck / [93] terminated with status 4
  mountall: Filesystem has errors: /

I must add, that at times the bios complains before, and resets. So maybe the hardware clock is wrong. But that was no problem with jaunty.

Getting this bug in kubuntu 12.04. My locale is VET, UTC=no in rcS.
Also, plymouth blinks so it doesn't get to show the error, but I know it's that one, so I have to boot to recovery mode and run fsck, which messes up the clock in order to adjust it to the "present"...

in precise, this causes my cable box to disconnect. the cable modem connects with the time wrong, ntp resets the time, dhclient then fails to renew the lease within the given time, and then Comcast terminates the connection.