https://bugzilla.novell.com/show_bug.cgi?id=695324 https://bugzilla.novell.com/show_bug.cgi?id=695324#c1 Marco Stornelli changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |X.Org AssignedTo|kernel-maintainers@forge.pr |bnc-team-xorg-bugs@forge.pr |ovo.novell.com |ovo.novell.com QAContact|qa@suse.de |xorg-maintainer-bugs@forge. | |provo.novell.com --- Comment #1 from Marco Stornelli 2011-05-28 09:29:26 UTC --- REassigned from kernel to X.Org because when the freeze happens, mouse works and remote access is possible, so the problem is related to X.Org and OpenGL. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=695324 https://bugzilla.novell.com/show_bug.cgi?id=695324#c2 --- Comment #2 from Marco Stornelli 2011-06-12 15:16:02 UTC --- Maybe the problem is here: commit d4aeee776017b6da6dcd12f453cd82a3c951a0dc "drm/i915: Disable pagefaults along execbuffer relocation fast path". The comment in the code says: "This is the fast path and we cannot handle a pagefault whilst holding the struct mutex lest the user pass in the relocations contained within a mmaped bo. For in such a case we, the page fault handler would call i915_gem_fault() and we would try to acquire the struct mutex again. Obviously this is bad and so lockdep complains vehemently. Indeed I see from the log kworker and cairo dock (after a fork) blocked on the same lock. This error has been fixed in 2.6.39 and I don't see the same fix in any version of 2.6.37. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=695324 https://bugzilla.novell.com/show_bug.cgi?id=695324#c4 --- Comment #4 from Marco Stornelli 2011-07-02 12:11:57 UTC --- The problem is confirmed, I built an ad-hoc module to test it and now? I'd like to see a new kernel version in the repo :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=695324 https://bugzilla.novell.com/show_bug.cgi?id=695324#c6 Marco Stornelli changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |greywolf82@hotmail.it --- Comment #6 from Marco Stornelli 2011-09-18 09:14:23 UTC --- I pretend a response. What other information do you need? I sent a debug report, I found the possible fix at kernel level, I tested a bug fix, have I to come to the suse headquarter to help you to build a new kernel? The maintain level is really horrible. If opensuse can't fix even obviously problem till the next version, I think you can close without any problem the bugzilla service, because it's really not needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=695324 https://bugzilla.novell.com/show_bug.cgi?id=695324#c8 --- Comment #8 from Marco Stornelli 2012-08-09 08:19:00 UTC --- I'm sorry but no excuse for this kind of behavior. The bug was opened on 22th May 2011!! More than one years ago!!! In addition it was really clear the problem, I sent you all the information, so the fix was really simple and fast. As I said, if you have got the only answer "wait for next release" you can close bugzilla without problems. And I repeat that the maintain level is really really horrible. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.