From the engineer debugging the case:
I noted there is one thing interesting and may be useful for your 3.9.3 backporting:
the i915 Call Trace message will appear when the system is: 1. 3.5.0-32(default) + 3.8.6 i915 backport dkms 2. 3.9.3
the i915 Call Trace message won't appear when the system is: 1. 3.5.0-32(default) without 3.8.6 i915 backport dkms 2. 3.10-rc3
only "3.5.0-32(default) + 3.8.6 i915 backport dkms" raised this bug, so I think the Call Trace message in comment 2 may not directly raise this bug
From the engineer debugging the case:
I noted there is one thing interesting and may be useful for your 3.9.3 backporting:
the i915 Call Trace message will appear when the system is:
1. 3.5.0-32(default) + 3.8.6 i915 backport dkms
2. 3.9.3
the i915 Call Trace message won't appear when the system is:
1. 3.5.0-32(default) without 3.8.6 i915 backport dkms
2. 3.10-rc3
only "3.5.0-32(default) + 3.8.6 i915 backport dkms" raised this bug,
so I think the Call Trace message in comment 2 may not directly raise this bug