On Mon, 27 Jun 2011 19:25:31 -0700 john stultz <johns...@us.ibm.com> wrote:
> On Sat, Apr 30, 2011 at 10:39 AM, Faidon Liambotis <parav...@debian.org> > wrote: > > We too experienced problems with just the G6 blades at near 215 days uptime > > (on the 19th of April), all at the same time. From our investigation, it > > seems that their cpu_clocks jumped suddenly far in the future and then > > almost immediately rolled over due to wrapping around 64-bits. > > > > Although all of their (G6s) clocks wrapped around *at the same time*, only > > one > > of them actually crashed at the time, with a second one crashing just a few > > days later, on the 28th. > > > > Three of them had the following on their logs: > > Apr 18 20:56:07 hn-05 kernel: [17966378.581971] tap0: no IPv6 routers > > present > > Apr 19 10:15:42 hn-05 kernel: [18446743935.365550] BUG: soft lockup - CPU#4 > > stuck for 17163091968s! [kvm:25913] > > So, did this issue ever get any traction or get resolved? > https://bugzilla.kernel.org/show_bug.cgi?id=37382 is similar - a divide-by-zero in update_sg_lb_stats() after 209 days uptime. Can we change this stuff so that the timers wrap after 10 minutes uptime, like INITIAL_JIFFIES? _______________________________________________ stable mailing list stable@linux.kernel.org http://linux.kernel.org/mailman/listinfo/stable
