Description of problem: Logs show issue with crond task, eventually system hangs. Last bit of output from /var/log/messages is attached (var-log-messages.txt)showing err's before system halted. Version-Release number of selected component (if applicable): RPM Group : System Environment/Base Source : cronie-1.0-7.fc9.src.rpm Yum Group : Base System/Base -> Type : Mandatory Build Time : Wed Jun 4 05:08:07 2008 Install Time : Thu Sep 25 11:05:44 2008 License : MIT and BSD Kernel Ver - Linux fedora64 2.6.26.3-29.fc9.x86_64 #1 SMP Wed Sep 3 03:16:37 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux Processor - AMD Athlon 64 3200+ 2Ghz Memory - 2GB RAM How reproducible: I dont know how to, it just happened.... Steps to Reproduce: 1.N/A 2.N/A 3.N/A Actual results: N/A Expected results: N/A Additional info: N/A
Created attachment 317866 [details] Logs Before Crash Logs Before Crash
You've probably found kernel bug. http://bugzilla.kernel.org/show_bug.cgi?id=10582
This might be fixed in 2.6.26.5-45, which got a lot of timer and clock fixes.
(In reply to comment #3) > This might be fixed in 2.6.26.5-45, which got a lot of timer and clock fixes. I noticed that 2.6.26.5-45 falls under the "updates-testing" repository. Should I be installing stuff from there, or will my system become unstable from installing things from "updates-testing" and "updates-testing-newkey"? Will it eventually be available in the main "updates" repository?
(In reply to comment #4) > (In reply to comment #3) > > This might be fixed in 2.6.26.5-45, which got a lot of timer and clock fixes. > > I noticed that 2.6.26.5-45 falls under the "updates-testing" repository. Should > I be installing stuff from there, or will my system become unstable from > installing things from "updates-testing" and "updates-testing-newkey"? Will it > eventually be available in the main "updates" repository? It's released.
Did 2.6.26.5-45 fix the problem?
I updated to 2.6.26.5-45 when the system advised that the update was available. Since the original occurrence the "blocked for more than 120 seconds" the system has not shown this behaviour in the logs especially after the upgrade to 2.6.26.5-45 kernel.