bz# 248954 says that it is reproducible on ASM startup, but this bug occurs on
an already running ASM/DB instance.
Are you sure this is really related to bz# 248954? The ASMlib, DB and kernel
versions differ and I cannot see no ia64_spinlock_contention on the kernel
backtrace. Is this related to bio?

I have no way to test both patches on this specific system. This is a mission
critical production machine. I have also a case opened on HP, but they are
taking too long to provide a solution for this problem.
ThatÂ´s why I filled a bug report on bugzilla hoping to get a faster response.
HP suggests to upgrade to version 2.6.9-56 (pre v4.6) but this is not yet
supported either by HP or RedHat, so thatÂ´s why we can not run those tests.
One thing that could be done is to backport those patches to supported RedHat
update so we can test it.

Please help get as much information as possible that are necessary to re-produce
the problem... if you think it is __not__ suitable on bugziila, you can direclty
send the info to my email account: luyu@redhat.com

yes, vmcore is helpful to analyze the problem. To fix the problem, it is also
very useful if the problem can be re-produced. So please help me get
information such as the machine type, the os version, the configuation, the
workloads,.... that others can try to use to reproduce the problem...

Please update the status of the bug, I'd like to know if the bug is just caused
by firmware/memory. If the problem still exists, I would try my best to
re-produce it. So far I'm not able to reproduce it.