[davismwfl]

You might check with a couple of the OS/hardware vendors too. I know Microsoft used to have labs on both east and west coasts that allow you to do this type of debugging, I would imagine they still do.

Sun used to do the same thing back in the day, not sure since Oracle took over, but it would be worth a call. IBM/HP also might have a lab environment where you can test on.

Maybe call the machine vendor your client used for that machine and explain what you need, you'd be surprised how accommodating they can be. It won't be free, but it likely is far far cheaper than a 60 core machine.

Good luck!

[sbenario]

Good idea! I'll check on that!

[techdragon]

If the software is running on RHEL, you should talk to Red Hat. I'm pretty sure that customers with a RHEL support contract can get access to application support from Red Hat to debug issues on the OS.

I also know first hand from Red Hat employees that they have a dedicated infrastructure for testing just this kind of "weird issue only happens on $foo hardware" stuff.

And while i can't confirm this as directly, I'm quite sure their hardware testing pool will contain some hardware that can help with debugging an issue like this.

[sbenario]

Indeed this was running on RHEL, though our client is a RHEL customer, and so far we aren't.