We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It seems we have a clock flooding problem using the image labriqueinternet_23-04-2015.img
labriqueinternet_23-04-2015.img
[133040.724366] clocksource hstimer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11945377789 ns [133042.223851] clocksource hstimer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 12574081885 ns [133042.974261] clocksource hstimer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11945377789 ns [133045.223207] clocksource hstimer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 13272641988 ns [133045.474149] clocksource hstimer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11945377789 ns
Event with a clock source change, the problem remain…
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource arch_sys_counter # cat /sys/devices/system/clocksource/clocksource0/available_clocksource arch_sys_counter timer hstimer
Possible help:
The text was updated successfully, but these errors were encountered:
Update Kernel config in order to try to fix bleuchtang#8
d2a2292
* Use stable 4.0 tarball. * Enable GENERIC_CLOCKEVENTS
Merge pull request #10 from sbadia/issue/8
27008b5
Update Kernel config in order to fix #8
Successfully merging a pull request may close this issue.
It seems we have a clock flooding problem using the image
labriqueinternet_23-04-2015.img
Event with a clock source change, the problem remain…
Possible help:
The text was updated successfully, but these errors were encountered: