Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263798AbTETRWS (ORCPT ); Tue, 20 May 2003 13:22:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263804AbTETRWS (ORCPT ); Tue, 20 May 2003 13:22:18 -0400 Received: from alpham.uni-mb.si ([164.8.1.101]:65274 "EHLO alpham.uni-mb.si") by vger.kernel.org with ESMTP id S263798AbTETRWR (ORCPT ); Tue, 20 May 2003 13:22:17 -0400 Date: Tue, 20 May 2003 19:34:55 +0200 From: David Balazic Subject: Wrong clock initialization To: linux-kernel@vger.kernel.org Message-id: <3ECA673F.7B3FB388@uni-mb.si> MIME-version: 1.0 X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) Content-type: text/plain; charset=iso-8859-2 Content-transfer-encoding: 7BIT X-Accept-Language: en Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 961 Lines: 33 Hi! When the kernel is booted ( ia32 version at least ) , it reads the time from from the hardware CMOS clock , _assumes_ it is in UTC and set the system time to it. As almost nobody runs their clock in UTC, this means that the system is running on wrong time until some userspace tool corrects it. This can lead to situtation when time goes backwards : timezone is 2hours east of UTC. UTC time : 20:00 local time : 22:00 System time between boot and userspace fix : 22:00UTC System time after fix : 20:00UTC Comments ? -- David Balazic -------------- "Be excellent to each other." - Bill S. Preston, Esq., & "Ted" Theodore Logan - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/