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.
JohnS wrote:That's my guess.
>
> 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.
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@centos.org
http://lists.centos.org/mailman/listinfo/centos