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

2013-11-28 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/592815 Ti

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

2013-09-29 Thread Christopher M. Penalver
Jeff Lane, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/curre

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

2010-06-22 Thread Jeremy Foshee
Jeff, yeah, I think pinging manoj is the right thing. He'll be the one to look at the bug anyway. :) Now all I need to do is finish up my flowchart for determining whether someone has tested upstream when the script runs. It is on the TODO. :) ~JFo -- Weird kernel timestamp jumping and incor

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

2010-06-22 Thread Jeff Lane
JFo, Yeah, I figured as much. :) I hadn't mentioned this to manjo yet, though maybe I should, since he was the one that pointed me to the PM instrumentation that was put into the kernel to mark power management events (which is part of what I'm using to determine sleep/resume times... at least

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

2010-06-22 Thread Jeremy Foshee
Jeff, Yep you've been victimized :-). ~JFo ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-needs-review kernel-power -- Weird kernel timestamp jumping and incorrect time reported in kernel m

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

2010-06-14 Thread Jeff Lane
Ahhh, I must have been caught by jfo's bug script :-) Please see comment #23 WRT to testing this with the upstream kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Tags removed: needs-upstream-testing -- Weird kernel timestamp jumping and incorrect time reported in ker

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

2010-06-14 Thread Jeremy Foshee
Hi Jeff, If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstrea

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

2010-06-11 Thread Jeff Lane
Also, I went ahead and re-tried this with the latest upstream kernel: Linux klaatu 2.6.35-999-generic #20100653 SMP Fri Jun 11 10:56:15 UTC 2010 x86_64 GNU/Linux and the behaviour is still there. Also, I finally realized the pattern which seems to be that the time jump only occurs after the

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

2010-06-11 Thread Jeff Lane
** Attachment added: "messages" http://launchpadlibrarian.net/50153016/messages -- 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 Ubuntu Bugs, which is subscrib

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

2010-06-11 Thread Jeff Lane
** 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