[Bug 592815] Re: Weird kernel timestamp jumping and incorrect time reported in kernel messages

Fri Jun 11 19:48:36 UTC 2010

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/50152120/Dependencies.txt

** Tags added: apport-collected

** Description changed:

  First, some history.  I really noticed this after doing some
  suspend/resume tests with a tool I've written.  I noticed it after
  adding in code to actually time the suspend and resume for each
  iteration I run in a loop.

  What I noticed is that, apparently, my laptop has been running for over
  18 Billion seconds.  Or not.

  Look in /var/log/messages which should be attached to this bug to see
  what I mean.  The important lines are between markers I inject through
  syslogd that look like ---CHECKBOX SLEEP TEST START <timestamp>--- and
  ---CHECKBOX SLEEP TEST END <timestamp>---.  Those mark the beginning and
  end of each suspend/resume iteration.

  Here are a few lines to give you an example of how the time is jumping
  around:

  Jun 11 11:16:28 klaatu kernel: [170340.742584] CPU 7 is now offline
  Jun 11 11:16:28 klaatu kernel: [170340.742587] SMP alternatives: switching to UP code
  Jun 11 11:16:28 klaatu kernel: [170340.749378] Extended CMOS year: 2000
  Jun 11 11:16:28 klaatu kernel: [18446744045.913778] CPU0: Thermal monitoring enabled (TM1)
  Jun 11 11:16:28 klaatu kernel: [18446744045.913839] Extended CMOS year: 2000
  Jun 11 11:16:28 klaatu kernel: [18446744045.913887] Enabling non-boot CPUs ...

  The first three lines are the final messages before the system fully
  enters S3 and reduces power.  The last three lines are the first
  messages when the system beings to wake. The time between suspend and
  wake is no more than 60 seconds in real time, but notices how I managed
  to go from 170,000 seconds since boot to 18.4 billion...

  I thought maybe it was just that I needed a reboot, so I did a reboot
  and tried this test again:

  Jun 11 11:22:30 klaatu kernel: [  175.191572] CPU 7 is now offline
  Jun 11 11:22:30 klaatu kernel: [  175.191574] SMP alternatives: switching to UP code
  Jun 11 11:22:30 klaatu kernel: [  175.197621] Extended CMOS year: 2000
  Jun 11 11:22:30 klaatu kernel: [18446744053.029258] CPU0: Thermal monitoring enabled (TM1)
  Jun 11 11:22:30 klaatu kernel: [18446744053.029263] CPU 0 MCA banks CMCI:8
  Jun 11 11:22:30 klaatu kernel: [18446744053.029323] Extended CMOS year: 2000

  So you can see that I did the suspend immediately after a fresh reboot
  and login.  The system had only been running for 175 seconds or so.
  BUT, again, the last three lines are the first messages during resume,
  and once more, the timestamps are showing 18 Billion seconds.

  Hardware:
  This is being seen on an Alienware M15x with a Quad Core i7 Intel chip and 4GB RAM.  
  The kernel is 2.6.32-22-generic 64 Bit from the latest 10.04 LTS updates
  I am NOT overclocking or anything like that, and I am NOT booting with any special parameters, this is a completely stock 10.04 LTS install.

  I'm not positive on how to recreate these steps.  The code in my test
  tool is simply doing things you can do manually:

  echo "+60" > /sys/class/rtc/rtc0/wakealarm
  pm-suspend

  Then after the system resumes, it checks the logs and calculates the
  time to suspend and time to resume using those timestamps.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-22-generic 2.6.32-22.36
  Regression: No
  Reproducible: No
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri Jun 11 15:32:06 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
+ AplayDevices:
+  **** List of PLAYBACK Hardware Devices ****
+  card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
+    Subdevices: 1/1
+    Subdevice #0: subdevice #0
+ Architecture: amd64
+ ArecordDevices:
+  **** List of CAPTURE Hardware Devices ****
+  card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
+    Subdevices: 1/1
+    Subdevice #0: subdevice #0
+ AudioDevicesInUse:
+  USER        PID ACCESS COMMAND
+  /dev/snd/controlC0:  bladernr   2312 F.... pulseaudio
+ CRDA: Error: [Errno 2] No such file or directory
+ Card0.Amixer.info:
+  Card hw:0 'Intel'/'HDA Intel at 0xf0f20000 irq 22'
+    Mixer name	: 'IDT 92HD83C1X5'
+    Components	: 'HDA:111d7604,102802a2,00100104'
+    Controls      : 16
+    Simple ctrls  : 10
+ Card1.Amixer.info:
+  Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
+    Mixer name	: 'Nvidia ID a'
+    Components	: 'HDA:10de000a,10de0101,00100100'
+    Controls      : 0
+    Simple ctrls  : 0
+ Card1.Amixer.values:
+  
+ DistroRelease: Ubuntu 10.04
+ HibernationDevice: RESUME=UUID=f4e6db09-5257-40b2-ba2a-0718fc0b3f0d
+ InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
+ MachineType: Alienware M15x
+ NonfreeKernelModules: nvidia
+ Package: linux (not installed)
+ ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=acc23352-13ab-4854-b1d7-a1099a5bf3a5 ro crashkernel=384M-2G:64M,2G-:128M quiet splash
+ ProcEnviron:
+  PATH=(custom, no user)
+  LANG=en_US.utf8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
+ Regression: No
+ RelatedPackageVersions: linux-firmware 1.34
+ Reproducible: Yes
+ Tags: lucid suspend resume needs-upstream-testing
+ Uname: Linux 2.6.32-22-generic x86_64
+ UserGroups:
+  
+ dmi.bios.date: 03/11/2010
+ dmi.bios.vendor: Alienware
+ dmi.bios.version: A05
+ dmi.board.vendor: Alienware
+ dmi.board.version: A05
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Alienware
+ dmi.chassis.version: A05
+ dmi.modalias: dmi:bvnAlienware:bvrA05:bd03/11/2010:svnAlienware:pnM15x:pvrA05:rvnAlienware:rn:rvrA05:cvnAlienware:ct8:cvrA05:
+ dmi.product.name: M15x
+ dmi.product.version: A05
+ dmi.sys.vendor: Alienware

-- 
Weird kernel timestamp jumping and incorrect time reported in kernel messages
https://bugs.launchpad.net/bugs/592815
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.