[Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
https://bugzilla.kernel.org/show_bug.cgi?id=106431 --- Comment #9 from poma --- Please push to linux-next and mainline 4.3. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
https://bugzilla.kernel.org/show_bug.cgi?id=106431 --- Comment #8 from poma --- Tested with: 4.3.0-2.fc22.i686 i.e. 4.3.0-1.fc24.i686 + nv-drm-vblank.patch https://bugzilla.kernel.org/attachment.cgi?id=191861 Tested-by: poma -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
https://bugzilla.kernel.org/show_bug.cgi?id=106431 --- Comment #7 from poma --- See Also: https://bugs.freedesktop.org/show_bug.cgi?id=92852 -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
https://bugzilla.kernel.org/show_bug.cgi?id=106431 --- Comment #6 from Ikey Doherty --- Above fixed confirmed as resolving nouveau functionality in X - however the 304 series driver from nvidia is not functional (whereas it's working on 4.1.12). (7600gt) P.S. I know the nvidia driver isn't anyone's issue here, more of a heads up for those who come looking for answers. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
https://bugzilla.kernel.org/show_bug.cgi?id=106431 --- Comment #5 from Ikey Doherty --- Created attachment 191861 --> https://bugzilla.kernel.org/attachment.cgi?id=191861=edit Revised version of Daniel's patch Added a revised version of Daniel's patch to include the symbol in the header. Validated on Solus, where the bug was actually worse and causing graphical "static" artefacts [1] https://plus.google.com/114713706129194876663/posts/DrUqQypp24w -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
https://bugzilla.kernel.org/show_bug.cgi?id=106431 Ikey Doherty changed: What|Removed |Added CC||ikey at solus-project.com --- Comment #4 from Ikey Doherty --- Hi - we've tested this in Solus Operating System as we encountered the same issue [1]. The patch required slight modification (exposing drm_arm_vblank_event via drmP.h) -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
https://bugzilla.kernel.org/show_bug.cgi?id=106431 --- Comment #3 from Daniel Vetter --- Created attachment 191661 --> https://bugzilla.kernel.org/attachment.cgi?id=191661=edit attempt at fixing pre-nv50 pageflip events Ok, I made an attempt at correctly fixing this, i.e. the 3rd option I laid out above. Patch attached, please test. Note that I'll be on vacation next 2 weeks, so Thierry needs to take over any follow-up work. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
https://bugzilla.kernel.org/show_bug.cgi?id=106431 Daniel Vetter changed: What|Removed |Added CC||daniel at ffwll.ch --- Comment #2 from Daniel Vetter --- Three ways to fix this: - open-code the old behaviour (without the warning) again in nouveau, just to shut it up. - don't register vblanks with the drm core (i.e. no call to drm_vblank_init) on pre-tesla if the hw/driver can't do it since it's just a lie apparently. According to following commit at least: commit af4870e406126b7ac0ae7c7ce5751f25ebe60f28 Author: Mario Kleiner Date: Tue May 13 00:42:08 2014 +0200 drm/nouveau/kms/nv04-nv40: fix pageflip events via special case. - fix up the underlying issue of sending the vblank events before they happen. Old intel hw is similar in that the pageflip irq from the hw happens when the flip arms, not when it completes at the next vblank. We solve that by enabling the corresponding vblank, and from the flip handler stuff the event someplace where the vblank handler can pick it up. Then on the next vblank we'll send out the event (knowing the timestamp to be accurate) and drop the vblank reference. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
https://bugzilla.kernel.org/show_bug.cgi?id=106431 Ilia Mirkin changed: What|Removed |Added CC||imirkin at alum.mit.edu --- Comment #1 from Ilia Mirkin --- Looks like this is because pre-tesla supplies a crtcid of -1 for pre-tesla (which your gpu is), and "pipe" was recently made into unsigned int, which causes the warn to trigger. J'accuse commit cc1ef118fc099295ae6aabbacc8af94d8d8885eb Author: Thierry Reding Date: Wed Aug 12 17:00:31 2015 +0200 drm/irq: Make pipe unsigned and name consistent Name all references to the pipe number (CRTC index) consistently to make it easier to distinguish which is a pipe number and which is a pointer to struct drm_crtc. While at it also make all references to the pipe number unsigned because there is no longer any reason why it should ever be negative. Signed-off-by: Thierry Reding Signed-off-by: Daniel Vetter -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
https://bugzilla.kernel.org/show_bug.cgi?id=106431 RussianNeuroMancer changed: What|Removed |Added Summary|dmesg is flooded with error |On ASUS A8JN laptop with |messages|G72M GPU dmesg is flooded ||with error messages -- You are receiving this mail because: You are watching the assignee of the bug.
