On Tue, Apr 12, 2016 at 12:53:47PM +0530, Krishna Kumar (Engineering) wrote: > This is actually a kernel Oops as it is accessing an invalid memory > location: fffffffffffffff4 (bug in code). Only kernel upgrade can fix that.
Yes and quite frankly with my kernel maintainer hat on, I'm having a hard time believing 2.6.24 to be stable in field. 2.6.22 and 2.6.25 used to be maintained for quite some extra time and appeared reasonably stable after several months of fixes, but it's from an era where nobody was yet sensibilized to tag fixes for stable backport and most important fixes were missing. Talk about 2.6.32.x, 3.2.x, 3.4.x or even 3.10.x as stable, but not 2.6.24. The fact that it happens to achieve years of uptime doing nothing is not a sign of stability. A stable kernel achieves years of uptime under stress and here apparently a simple recvform() syscall is enough to crash it under certain conditions :-/ Regards, Willy
