As has been reported in previous alogs, the 2.6.34 kernel has a timer counter overflow bug with makes the machines susceptible to freeze-up if they have been running in excess of 208.5 days. Last week h1build froze, and this weekend h1seiey, h1susauxb123 and h1susauxh34 did the same. The machines marked with an asterix in the list below have an uptime which exceeds 208.5 and could freeze at any time. We should work on verfifying their SDF settings are up to date and then reboot them at our earliest convenience.
* h1psl0 up 211 days
* h1seih16 up 211 days
* h1seih23 up 211 days
* h1seih45 up 211 days
* h1seib1 up 211 days
* h1seib2 up 211 days
* h1seib3 up 211 days
h1sush2a up 58 days
h1sush2b up 201 days
* h1sush34 up 211 days
h1sush56 up 192 days
* h1susb123 up 211 days
* h1susauxh2 up 211 days
h1susauxh34 up 7:01
h1susauxh56 up 191 days
h1susauxb123 up 7:03
h1oaf0 up 61 days
h1lsc0 up 58 days
h1asc0 up 202 days
* h1pemmx up 209 days
* h1susauxey up 211 days
h1susey up 38 days
* h1iscey up 211 days
* h1susauxex up 211 days
* h1susex up 211 days
h1seiex up 95 days
h1iscex up 163 days
This is a temporary problem, following LLO we will be upgrading all LHO front ends and DAQ machines to newer kernels (which do not have this bug) in the near future.
Here is the alog which initially discussed this bug alog 35901