[Bug 436076] Re: system clock not adjusted when hardware clock in localtime

[gregrwm]

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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/436076

Title:
  system clock not adjusted when hardware clock in localtime

Status in “util-linux” package in Ubuntu:
  Fix Released
Status in “util-linux” source package in Karmic:
  Fix Released

Bug description:
  Binary package hint: util-linux

  Since the Upstart migration, we appear to have regressed on this
  again.

  The system clock doesn't get adjusted to UTC when the hardware clock
  is in localtime.

  This will cause one of the following two errors on boot:

    hwclock main process (85) terminated with status 1

  or (worse):

    /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: /

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/436076/+subscriptions