> Thank you for taking the time to write. Having said
> where I stand and we are kind of on the same page. Is
> there something I can expect which would put me on a
> track of nailing down the problem. It maybe a wild
> goose chase but something that I can start with would
> be much appreciated.
Just random debugging thoughts...
Try stock 18.104.22.168, to see if you have the same problem. If so, and
esp. if you also see it on 2.6.29, then you'll get a lot more attention
If not, then it's something with your backport most likely. Figure out
what you had to backport and see if it's possibly causing the error(s).
If it's locked up, try sysrq-w (echo w > /proc/sysrq-trigger) and look
at dmesg to see if other threads are locked against it. Figure out why.
On the oops try memory debugging etc, see if you're referencing freed
memory, using corrupt lists, etc.
Look for other errors in the logs prior to this.
See if your filesystem is corrupted.
Bug Red Hat for XFS support, assuming you're actually buying RHEL5
support from them. :)
> Unfortunately there is no distro which gets closer to
> where mainline lives today. Reading the changelog
> there are several problems that I have already come
> across and has convincingly driven me to take on this
well certainly there are distros with kernels newer than 2.6.18, but it
depends on your needs & goals I guess.