crash icon indicating copy to clipboard operation
crash copied to clipboard

Uptime on arm64 not being computed correctly

Open stevecapperlinaro opened this issue 7 years ago • 1 comments

Hi, We are getting uptime values based off of jiffies values in crash. Unfortunately, on arm64, the CPU frequency is assumed to be 100Hz and this causes unrealistic uptimes to be reported.

Is it possible to follow the kernel approach to computing uptime from, get_monotonic_boottime(.), with something like: uptime in nano-seconds = (tk_core->timekeeper->tkr_mono->base + tk_core->timekeeper->offs_boot) From: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/time/timekeeping.c?h=v4.12#n782

Cheers, Steve

stevecapperlinaro avatar Jul 26 '17 09:07 stevecapperlinaro

----- Original Message -----

Hi, We are getting uptime values based off of jiffies values in crash. Unfortunately, on arm64, the CPU frequency is assumed to be 100Hz and this causes unrealistic uptimes to be reported.

Is it possible to follow the kernel approach to computing uptime from, get_monotonic_boottime(.), with something like: uptime in nano-seconds = (tk_core->timekeeper->tkr_mono->base + tk_core->timekeeper->offs_boot) From: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/time/timekeeping.c?h=v4.12#n782

Cheers, Steve

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/crash-utility/crash/issues/17

Please feel free to file a patch to [email protected], which is the mailing list for proprosed patches:

https://www.redhat.com/mailman/listinfo/crash-utility

Thanks, Dave

crash-utility avatar Aug 07 '17 14:08 crash-utility