[Bug 58361] [REGRESSION][BISECTED] Commit ea9b43ad causes stack traces on i915

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=58361





--- Comment #3 from Rogério Brito <rbrito at ime.usp.br>  2013-05-17 08:43:09 ---
Dear Takashi,

(In reply to comment #2)
> Are you seeing this in 3.8.y kernel, or 3.9 kernel?  From your description, it
> sounds like you're seeing the problem in 3.8.y stable kernel while the earlier
> 3.8 didn't show it.  Or, do you mean that it starts showing with 3.9 while 3.8
> didn't?

Oops, let me clear the confusion:

* I first saw the problem with Debian's 3.8.y stable kernel, which (obviously)
includes the patches that were marked to stable (the case of the patch in
question).

* I booted with Ubuntu's precompiled snapshot "mainline" kernels of version
3.10-rc1, which should be pristine as they announce (just to save me the
trouble of compilation).

* Then, I grabbed Linus kernel and did the bisecting in *his* kernel and found
your commit as the one that broke my system.

> In either way, simply try to revert the commit you spotted.  It *must* fix the
> problem, if the bisection were correct.

I reverted, compiled, tested and things seem fixed.

For my tests, I included logging out of X (which was one source of such stack
traces) and hibernating (which was another source of the stack traces).

They don't happen anymore with the commit reverted.

I hope that this clears the situation. If you need any other data (dumps,
configurations etc.), please let me know.


Thanks for the quick reply,

Rogério Brito.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.