Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2015-04-26 Thread Richard Weinberger
Hi! Am 26.04.2015 um 22:57 schrieb Thomas Meyer: > Am Sonntag, den 26.04.2015, 20:32 +0200 schrieb Richard Weinberger: >> On Fri, Apr 24, 2015 at 9:58 PM, Thomas Meyer wrote: >>> Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger: Am 20.10.2014 um 11:51 schrieb Thomas Meyer:

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2015-04-26 Thread Thomas Meyer
Am Sonntag, den 26.04.2015, 20:32 +0200 schrieb Richard Weinberger: > On Fri, Apr 24, 2015 at 9:58 PM, Thomas Meyer wrote: > > Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger: > >> Am 20.10.2014 um 11:51 schrieb Thomas Meyer: > >> >> Hmm, does this always happen? > >> > > >> >

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2015-04-26 Thread Richard Weinberger
Am 26.04.2015 um 20:32 schrieb Richard Weinberger: > On Fri, Apr 24, 2015 at 9:58 PM, Thomas Meyer wrote: >> Any ideas? > > Can you give the attached patch a try? > Let's see if it proves my theory. > Looks like UML's clocksource needs fixing. Please give also this patch a try. I should fix

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2015-04-26 Thread Richard Weinberger
On Fri, Apr 24, 2015 at 9:58 PM, Thomas Meyer wrote: > Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger: >> Am 20.10.2014 um 11:51 schrieb Thomas Meyer: >> >> Hmm, does this always happen? >> > >> > Yes, my single core system seems to trigger this every time after resume >> >

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2015-04-26 Thread Richard Weinberger
Am 26.04.2015 um 20:32 schrieb Richard Weinberger: On Fri, Apr 24, 2015 at 9:58 PM, Thomas Meyer tho...@m3y3r.de wrote: Any ideas? Can you give the attached patch a try? Let's see if it proves my theory. Looks like UML's clocksource needs fixing. Please give also this patch a try. I should

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2015-04-26 Thread Richard Weinberger
Hi! Am 26.04.2015 um 22:57 schrieb Thomas Meyer: Am Sonntag, den 26.04.2015, 20:32 +0200 schrieb Richard Weinberger: On Fri, Apr 24, 2015 at 9:58 PM, Thomas Meyer tho...@m3y3r.de wrote: Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger: Am 20.10.2014 um 11:51 schrieb Thomas

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2015-04-26 Thread Thomas Meyer
Am Sonntag, den 26.04.2015, 20:32 +0200 schrieb Richard Weinberger: On Fri, Apr 24, 2015 at 9:58 PM, Thomas Meyer tho...@m3y3r.de wrote: Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger: Am 20.10.2014 um 11:51 schrieb Thomas Meyer: Hmm, does this always happen? Yes,

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2015-04-26 Thread Richard Weinberger
On Fri, Apr 24, 2015 at 9:58 PM, Thomas Meyer tho...@m3y3r.de wrote: Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger: Am 20.10.2014 um 11:51 schrieb Thomas Meyer: Hmm, does this always happen? Yes, my single core system seems to trigger this every time after resume

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2015-04-24 Thread Thomas Meyer
Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger: > Am 20.10.2014 um 11:51 schrieb Thomas Meyer: > >> Hmm, does this always happen? > > > > Yes, my single core system seems to trigger this every time after resume > > from ram. > > What is your host kernel? > > >> At least on

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2015-04-24 Thread Thomas Meyer
Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger: Am 20.10.2014 um 11:51 schrieb Thomas Meyer: Hmm, does this always happen? Yes, my single core system seems to trigger this every time after resume from ram. What is your host kernel? At least on my notebook it

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2014-10-20 Thread Thomas Meyer
Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger: > Am 20.10.2014 um 11:51 schrieb Thomas Meyer: > >> Hmm, does this always happen? > > > > Yes, my single core system seems to trigger this every time after resume > > from ram. > > What is your host kernel? The standard Fedora

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2014-10-20 Thread Richard Weinberger
Am 20.10.2014 um 11:51 schrieb Thomas Meyer: >> Hmm, does this always happen? > > Yes, my single core system seems to trigger this every time after resume from > ram. What is your host kernel? >> At least on my notebook it did not happen. I've started an UML yesterday >> suspended it and

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2014-10-20 Thread Thomas Meyer
Am 20.10.2014 10:27 schrieb Richard Weinberger : > > On Sun, Oct 19, 2014 at 2:39 PM, Thomas Meyer wrote: > > Hello, > > > > in UML kernel I get a long cpu using loop in __getnstimeofday() > > (kernel/time/timekeeping.c:315) in the call of timespec_add_ns(), > > when I left the host kernel

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2014-10-20 Thread Richard Weinberger
On Sun, Oct 19, 2014 at 2:39 PM, Thomas Meyer wrote: > Hello, > > in UML kernel I get a long cpu using loop in __getnstimeofday() > (kernel/time/timekeeping.c:315) in the call of timespec_add_ns(), > when I left the host kernel suspended to ram for a few hours and resume > again. > this is

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2014-10-20 Thread Richard Weinberger
On Sun, Oct 19, 2014 at 2:39 PM, Thomas Meyer tho...@m3y3r.de wrote: Hello, in UML kernel I get a long cpu using loop in __getnstimeofday() (kernel/time/timekeeping.c:315) in the call of timespec_add_ns(), when I left the host kernel suspended to ram for a few hours and resume again. this

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2014-10-20 Thread Thomas Meyer
Am 20.10.2014 10:27 schrieb Richard Weinberger richard.weinber...@gmail.com: On Sun, Oct 19, 2014 at 2:39 PM, Thomas Meyer tho...@m3y3r.de wrote: Hello, in UML kernel I get a long cpu using loop in __getnstimeofday() (kernel/time/timekeeping.c:315) in the call of timespec_add_ns(),

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2014-10-20 Thread Richard Weinberger
Am 20.10.2014 um 11:51 schrieb Thomas Meyer: Hmm, does this always happen? Yes, my single core system seems to trigger this every time after resume from ram. What is your host kernel? At least on my notebook it did not happen. I've started an UML yesterday suspended it and after more

Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram

2014-10-20 Thread Thomas Meyer
Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger: Am 20.10.2014 um 11:51 schrieb Thomas Meyer: Hmm, does this always happen? Yes, my single core system seems to trigger this every time after resume from ram. What is your host kernel? The standard Fedora kernel:

[UM] Long loop in __getnsdayoftime() after resume from ram

2014-10-19 Thread Thomas Meyer
Hello, in UML kernel I get a long cpu using loop in __getnstimeofday() (kernel/time/timekeeping.c:315) in the call of timespec_add_ns(), when I left the host kernel suspended to ram for a few hours and resume again. this is because it seems like the tk->xtime_sec wasn't updated yet, but the nsecs

[UM] Long loop in __getnsdayoftime() after resume from ram

2014-10-19 Thread Thomas Meyer
Hello, in UML kernel I get a long cpu using loop in __getnstimeofday() (kernel/time/timekeeping.c:315) in the call of timespec_add_ns(), when I left the host kernel suspended to ram for a few hours and resume again. this is because it seems like the tk-xtime_sec wasn't updated yet, but the nsecs