similar to: [Bug 63192] drmModeSetCursor->nouveau_bo_rd32->ioread32 provides high cpu load when using weston drm-compositor

https://bugs.freedesktop.org/show_bug.cgi?id=34969 Pierre Moreau <pierre.morrow at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|DRM/other |Driver/nouveau Version|XOrg git

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #26 from Pekka Paalanen <ppaalanen at gmail.com> --- What did the -1 as crtc mean? I'm not sure how this is weston-specific, though. Weston programs a pageflip on a certain crtc, and then relies on that particular crtc to send back a pageflip event as requested. So if that's the culprit, is Nouveau on some particular

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #29 from Pekka Paalanen <ppaalanen at gmail.com> --- Hmm, a third remote possibility came to mind. If the timestamp delivered with the DRM pageflip event does not advance, I suppose Weston's fade-in animation might not advance either and therefore it never fades in. However this is hard for me to believe, as I think it would

https://bugs.freedesktop.org/show_bug.cgi?id=108651 --- Comment #2 from Yuxuan Shui <yshuiv7 at gmail.com> --- compton itself does not have lots of dependencies. Right now all the users experienced this problem seems to be using the i3 window manager, I don't know if this is reproducible with windowmaker. I don't know the mesa version they use, I will ask. But judging that they are

https://bugs.freedesktop.org/show_bug.cgi?id=92893 Bug ID: 92893 Summary: NV34: XPresent compositor scrambled Product: xorg Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=109631 Bug ID: 109631 Summary: Moving gbm bo from GART to VRAM does not wait for rendering Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #32 from Pekka Paalanen <ppaalanen at gmail.com> --- (In reply to comment #31) > Created attachment 100199 [details] > weston log with pixman Something is seriously wrong here: [09:58:29.402] queueing pageflip failed: Permission denied But I see you have another weston session afterwards, which seems to run, but:

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #28 from Pekka Paalanen <ppaalanen at gmail.com> --- I wonder if there are two different bugs in play here. If you do get the vblank events right, like it sounds that Nerdopolis does indeed get, then does reverting the blamed nouveau kernel patch make any difference? I would be surprised if it does make a difference. This

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #27 from nerdopolis1 at verizon.net --- I pulled out my old Dell desktop with a Pentium 4 processor, and AGB Nvidia card (NV36), and it does the same thing. Mark45 on Phoronix said this issue affected all 3 of his Nvidia cards when he tried to use my Wayland Live CD. I added the "got pageflip event" lines as suggested, and

From: Christopher James Halse Rogers <raof at ubuntu.com> Barring some (admittedly significant) missing optimisations? this is reasonably complete, but can't be applied until the Xserver patch has landed, and that needs more work. This demonstrates the approach, however. There's probably some code to be shared with XWayland support, around the output handling (or lack thereof) and

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #24 from Lubosz Sarnecki <lubosz at gmail.com> --- Since Weston and Wayland 1.5.0 were released today, I wanted to ask about the status of this bug. Does the patch which causes the regression have enough legitimacy to stay and break Weston? Does someone understand the problem on a large scale? -- You are receiving this mail

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #25 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #24) > Since Weston and Wayland 1.5.0 were released today, I wanted to ask about > the status of this bug. > > Does the patch which causes the regression have enough legitimacy to stay > and break Weston? It seems like a pretty correct fix,

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #34 from nerdopolis1 at verizon.net --- Just an FYI, I think the [09:58:29.402] queueing pageflip failed: Permission denied came from when I killed the previous Weston session, to have the waylandloginmanager reload Weston after I recompiled it with the diag lines on my live session. I was in another TTY That was the only time I

https://bugs.freedesktop.org/show_bug.cgi?id=55596 Priority: medium Bug ID: 55596 Assignee: nouveau at lists.freedesktop.org Summary: weston-launch causes graphical corruption / lockup Severity: major Classification: Unclassified OS: Linux (All) Reporter: vekinn at gmail.com Hardware: x86-64 (AMD64)

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|wayland-bugs at lists.freedesk |nouveau at lists.freedesktop.o |top.org |rg QA Contact|

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW --- Comment #12 from Pekka Paalanen <ppaalanen at gmail.com> --- Setting status to NEW, since this

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #18 from Lubosz Sarnecki <lubosz at gmail.com> --- I was able to boot all commits with following boot option: nouveau.config=NvMSI=0 Thanks to xexaxo on the IRC for pointing out this option. f074d733866628973eca0ddb0c534ef4561da9e0 is the first bad commit commit f074d733866628973eca0ddb0c534ef4561da9e0 Author: Maarten

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #19 from Lubosz Sarnecki <lubosz at gmail.com> --- Reverting the patch on current Linux master (4a4389abdd9822fdf3cc2ac6ed87eb811fd43acc) fixes the issue for me. Apperently s->crtc needs to be hardcoded to -1 for the screen not to stay black when launching weston. -- You are receiving this mail because: You are the

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #31 from nerdopolis1 at verizon.net --- Created attachment 100199 --> https://bugs.freedesktop.org/attachment.cgi?id=100199&action=edit weston log with pixman -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #33 from Pekka Paalanen <ppaalanen at gmail.com> --- I filed bug #79502 for adding the detection to Weston. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: