I can't agree with rakib on the solution he suggested although his analysis make sense.
The msm_vibrator_power() is called in hrtimer handler. And hrtimer is running in software irq context.
The OOPS information complains that msm_vibrator_power() calls _regulator_get() which uses mutex inside it.
The solution to this issue is: avoid to use any blocking/sleeping functions inside the hrtimer handler. That means to re-design the hrtimer handler, avoid to call mutex() kinds of blocking/sleeping functions.