From: Willy Tarreau <w@1wt.eu>
To: Frans Pop <elendil@planet.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Time travel experiment?
Date: Wed, 10 Sep 2008 23:28:40 +0200 [thread overview]
Message-ID: <20080910212840.GA24654@1wt.eu> (raw)
In-Reply-To: <200809101825.29276.elendil@planet.nl>
On Wed, Sep 10, 2008 at 06:25:28PM +0200, Frans Pop wrote:
> 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.
Note that the time jump is 500 million seconds in the future (498977611
to be precise). I don't know if it is possible that some value running
one unit has mistakenly been used in place of another one (eg: internal
clock ticks instead of jiffies, etc...).
Willy
next prev parent reply other threads:[~2008-09-10 21:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 14:58 Time travel experiment? Frans Pop
2008-09-10 14:29 ` Alan Cox
2008-09-10 15:55 ` Frans Pop
2008-09-10 16:25 ` Frans Pop
2008-09-10 16:56 ` Frans Pop
2008-09-10 17:02 ` Linus Torvalds
2008-09-10 18:07 ` [patch] Document use of RTC in pm_trace Frans Pop
2008-09-13 11:20 ` Pavel Machek
2008-09-10 21:28 ` Willy Tarreau [this message]
2008-09-10 20:47 ` Time travel experiment? Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080910212840.GA24654@1wt.eu \
--to=w@1wt.eu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.