From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754691AbYIJQZo (ORCPT ); Wed, 10 Sep 2008 12:25:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754495AbYIJQZd (ORCPT ); Wed, 10 Sep 2008 12:25:33 -0400 Received: from cpsmtpo-eml06.kpnxchange.com ([213.75.38.155]:39495 "EHLO cpsmtpo-eml06.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752305AbYIJQZc (ORCPT ); Wed, 10 Sep 2008 12:25:32 -0400 From: Frans Pop To: Alan Cox Subject: Re: Time travel experiment? Date: Wed, 10 Sep 2008 18:25:28 +0200 User-Agent: KMail/1.9.9 References: <200809101658.06935.elendil@planet.nl> <20080910152917.634a03fc@the-village.bc.nu> <200809101755.19927.elendil@planet.nl> In-Reply-To: <200809101755.19927.elendil@planet.nl> Cc: linux-kernel@vger.kernel.org, Thomas Gleixner MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809101825.29276.elendil@planet.nl> X-OriginalArrivalTime: 10 Sep 2008 16:25:30.0343 (UTC) FILETIME=[D767CF70:01C91361] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 10 September 2008, Frans Pop wrote: > > > $ date > > > Wed Jul 3 23:09:23 CEST 2024 > > > > Is this repeatable ? > > This wasn't the first suspend I've done today and I'd not seen it > before. I'll follow up if it does repeat, but I thought it was strange > and potentially important enough to at least report this occurrence. It > might ring a bell with someone. Oops. Yes, it is repeatable. Just had the same occur again. Not sure if I can trigger it reliably though or if it will still happen after a reboot. The jump occurs at the same point and to almost the same time/date: Sep 10 18:15:30 aragorn kernel: PM: Adding info for No Bus:vcs63 Sep 10 18:15:30 aragorn kernel: PM: Adding info for No Bus:vcsa63 Sep 10 18:15:30 aragorn kernel: wlan0: authenticate with AP 00:14:c1:38:e5:15 Sep 10 18:15:30 aragorn kernel: wlan0: authenticated Sep 10 18:15:30 aragorn kernel: wlan0: associate with AP 00:14:c1:38:e5:15 Sep 10 18:15:30 aragorn kernel: wlan0: RX ReassocResp from 00:14:c1:38:e5:15 (capab=0x411 status=0 aid=1) Sep 10 18:15:30 aragorn kernel: wlan0: associated Sep 10 18:15:30 aragorn kernel: PM: Removing info for No Bus:vcs63 Sep 10 18:15:30 aragorn kernel: PM: Removing info for No Bus:vcsa63 Jul 3 23:09:01 aragorn kernel: wlan0: disassociating by local choice (reason=3) Jul 3 23:09:03 aragorn kernel: wlan0: associate with AP 00:14:c1:38:e5:15 Jul 3 23:09:03 aragorn kernel: wlan0: RX ReassocResp from 00:14:c1:38:e5:15 (capab=0x411 status=0 aid=1) One other thing with this last one. I had the system on AC this time, which means the screensaver was active. It was running at a crazy speed (much too fast). If I start the screensaver again now it runs at normal speed.