On Sat 2007-07-21 09:54:37, Bill Davidsen wrote:
> Ken Moffat wrote:
> >On Fri, Jul 20, 2007 at 10:42:15AM -0700, Randy Dunlap
> >wrote:
> >
> >>man uptime:
> >> uptime - tell how long the system has been running
> >>
> >>I claim that the system is not running when it is
> >>suspended,
> >>so the suspension time should not be included in
> >>uptime.
> >>
> >>
> > So, maybe I shouldn't have put corrected in inverted
> > commas,
> >because this was a real correction and my previous
> >usage was an
> >unintended side-effect of an error.
> >
> > Anyway, the current behaviour is known and I guess any
> > attempt to
> >change it (e.g. to what Bill was expecting) won't be
> >well received.
> >
>
> So is setting it to a random number considered correct
> behavior? Any of the first three values I mentioned
> would make sense, but the value I see is neither time
> since resume, time since power-on to do the resume, or
> any of the logical uptime values. That was the whole
> point of the original post, the uptime reported makes no
> sense at all.
Ouch, seems like something is wrong with timer subsystem. Can you
verify that rest of the clock machinery behaves ok?
We do manual correction of uptime during resume (IIRC) - perhaps
something goes wrong there?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
