Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp17646414ybl; Thu, 2 Jan 2020 09:17:46 -0800 (PST) X-Google-Smtp-Source: APXvYqxf20OwyndzGdxZQR9ml4I0TFZvGczqIcshTW4EEQezU2+QaK/3LuNGp8HQw6X9V3hAIevj X-Received: by 2002:a9d:478:: with SMTP id 111mr91564293otc.359.1577985466766; Thu, 02 Jan 2020 09:17:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577985466; cv=none; d=google.com; s=arc-20160816; b=asw1glckQ6B9RYzJVl3r7EA1SZG46n2LRSkZLsGJb0LlTcbEPVSZ9Pjvoy+Y8dvfXU P2qaH0xPrxLWwbRS1d5fl40iOnGa6jrV4jgcs2pJctaoMxkj8T4HWRXG/HcMZy51BLCn DfxqUNSg8BrVjXEbXopJVwPkbaYld+4/3S1F8Q/d/Cr5G7W1LLFlZBVg8j+KdTp8ImEZ X3xw7tJiovEVVVUT7tcp6gJmaNM3gDjU3uFT68RZw6Ob6QGAjEHQp5R8LES7FdL2ZiVy 50m4g73VN2ajJK8CAioGW9Sfc2NfYJVRV13NHCHelDBBNh9TocjMKP8VH22nPqWX8DgH QFAA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=egyXgieBs5c/58fAQVjRHfzS4DxpEu8BEyJ/qKWY5yY=; b=qGTs7U2A8uUvTye1TpEAbV0tax80RLtunZz0/p+rHNWGQqlnyBSEKETl1nguro4nL7 LgBBhd/KBRZbutJf6JpXH4nyXFRXudeyhAQ/lZjelcov5STnvAnwMu0qWZlV92tG4eU3 OOi/8q4hlrBgMVinEoydwS+pxsDtAojluKwyE08heQHP+Zkss7rqEAqBRhRd396DVxYj 4GDv5uFgULU/K+BHtn8jP9wqy4A6CHXsOsa7PymQ0QdDFRY0sKm11DZ440GGYE7Ue65O phVhSVP5BkBYetGgoHhAhurqKwzNQsAKfsnBnME+h9t/R0qZnQE0Kbz4c+lhwpm9ThMj D0Ug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Pg7fbNui; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z14si29692456oth.15.2020.01.02.09.17.34; Thu, 02 Jan 2020 09:17:46 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Pg7fbNui; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727810AbgABRQr (ORCPT + 99 others); Thu, 2 Jan 2020 12:16:47 -0500 Received: from mail-il1-f177.google.com ([209.85.166.177]:35167 "EHLO mail-il1-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726125AbgABRQr (ORCPT ); Thu, 2 Jan 2020 12:16:47 -0500 Received: by mail-il1-f177.google.com with SMTP id g12so34614675ild.2; Thu, 02 Jan 2020 09:16:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=egyXgieBs5c/58fAQVjRHfzS4DxpEu8BEyJ/qKWY5yY=; b=Pg7fbNui9RfYxQvdhHBfqpZMWRrdKqsMWbD4Jbdauim2JS3GH6VapXgC4MOQ2Yp/qC 2sRxyssOPLh1zkb5qAPXbK8t5erANtYvScTa7Bq32wd3+dplBCC0nNOhJ3+qRtPb9IzM AU4fFD/7IkjeXmfq21MJTejKao/O9t2nKbtxMPi4wNER73mQaQJ32rQd/V+fr1dAN6WY TWicbi8tVsBFT2/ZRZoz8UCQzd47+cUaYfxsk1qioi0bKmTjxEGyxScjDvRX37t/Navp VsAssjemYKbQewu7UONx9fBHi7p0vq0dTKHAX0B5KCoSuv+ErhAujgAXTlq+nCDmA3mM 5YsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=egyXgieBs5c/58fAQVjRHfzS4DxpEu8BEyJ/qKWY5yY=; b=M1EJKXt/ZG2bl9rYwC974iGQ+OUnMSA2uCjS1IpjVShhGGfFzLQ+oOi+JmyWzobhHU zEM9zJmucRV1Gl/Sbzq6mx+kLM5Q5aKmPgxP5d7/6Jq9oYwTF3zG17dQxN9UW9QcjG+/ twZ0npaYffSB1BYe3bcb3rQY7BjniVCFnCIuJYOu25JaF2FPgmZ4N18iAT35We1nQsmz QXi+gDYozCa5lOmuTODTywvx9zmjDh5thQ0nzZl3PTx0+P3/7NJTmVl46R4nMfrex5SG QkTrKx8y3LwixqqqLLQ3rxR3sIFcaGqxqHH85RRMFTNGfjFYdiLurGJSMjSUcHgwDNK0 /x3A== X-Gm-Message-State: APjAAAU17YZeJkZTbfLD8dl3ox53ds7t5nuS0Qh7xHH7j8Uq6asLOCSG vLKEepUCiA4PfnEwJPIyqNMjipDMYTyS/4gzwII= X-Received: by 2002:a92:b6d1:: with SMTP id m78mr53509204ill.245.1577985406559; Thu, 02 Jan 2020 09:16:46 -0800 (PST) MIME-Version: 1.0 References: <20200101141748.GA191637@mit.edu> <20200102110817.ahqaqidw3ztw3kax@10.255.255.10> <20200102131434.tky2hquki23laqqo@10.255.255.10> In-Reply-To: From: Mikhail Gavrilov Date: Thu, 2 Jan 2020 22:17:26 +0500 Message-ID: Subject: Re: [bugreport] "hwclock -w" reset time instead of setting the right time To: J William Piggott Cc: Karel Zak , util-linux@vger.kernel.org, Linux List Kernel Mailing , linux-rtc@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2 Jan 2020 at 21:59, J William Piggott wrote: > > You've demonstrated that 'hwclock -w' does not 'reset' the RTC. > > Does your new motherboard use a battery backup for the RTC? > Is the battery good? > If you look carefully demonstration the RTC 'reset' happens after reboot __only__ when 'hwclock -w' have been entered before reboot. So if I reboot the computer without 'hwclock -w' the RTC will be not reset. -- Best Regards, Mike Gavrilov.