Actually, I've also been experience this issue on a two identical custom built systems running 5.3 x64 with Xen. I experienced the issue under the same kernel that Peter is running and the first kernel released with 5.3. In my particular instance, I'm attributing these random crashes to hardware problems since I'm only experiencing the issues on these two systems and not an older Dell PowerEdge 850 which is set up with the same software configuration. Matt -- Mathew S. McCarrell Clarkson University '10 mccarrms at gmail.com mccarrms at clarkson.edu On Fri, May 22, 2009 at 10:26 AM, Michael A. Peters <mpeters at mac.com> wrote: > JohnS wrote: > > > > > My sejustion is unplug everything hooked to it but the power and network > > cabling. Open it up while it is running, and shake the cables lightly > > ( don't jerk on them). External disk array, unplug it also. USB floppies > > and cd drives unplug emmm all. > > > > Is it under a heavy load? High cpu usage? Some times when there is a > > power supply on the verge of dying you don't really know until disk I/O > > climbs real high thus pulling loads of wattage. > > That's my guess. > I'd swap out the power supply. > > My personal experience with ram issues is either kernel panic or > filesystem funnyness (sometimes resulting in filesystems being remounted > read only). My experience with disk I/O issues is that forcing fsck > reveals filesystem errors with high frequency. > > Rebooting machines in my experience is almost always a failing power > supply (or faulty power source - check your UPS, when they start to go > bad they can cause issues). > > If it was a kernel issue, I suspect more people would be experiencing > (unless it is caused by a third party kmod) > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20090522/2a52ad91/attachment-0005.html>