similar to: [Bug 69876] [NVC3] Reverse prime sometimes freezes the machine

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #12 from Mike <michele.cane at gmail.com> --- I dropped Gnome and I now use Compton as compositor and the problem is no more present. I do not know if is due to newer kernel 3.16 or is a compositor related issue. Cheers Michele Cane, PhD. Sent from my Android device. On Aug 21, 2014 11:25 PM, <bugzilla-daemon at

https://bugs.freedesktop.org/show_bug.cgi?id=69876 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Revers prime sometime |[NVC3] Reverse prime |freezes the machine |sometimes freezes the |

https://bugs.freedesktop.org/show_bug.cgi?id=69876 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #9 from Mike <michele.cane at gmail.com> --- When nouveau.runpm=0 no freeze occurs. -- 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=69876 --- Comment #3 from Mike <michele.cane at gmail.com> --- With 3.10 is working fine. Have not tried with 3.11. I recompiled 3.12-rc1 without vgaswitcheroo and the problem persists. -- 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=69876 --- Comment #4 from Kevin N. <vekinn at gmail.com> --- I experience the same thing with my Thinkpad t530 and NVS 5400m in Optimus mode with 3.12-rc2 on Fedora 19. Locks up if I use xrandr or try to do anything with the displayport unless I have it plugged in at boot. Works fine if I change in bios to discrete nvidia. -- You are

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #5 from Emil Velikov <emil.l.velikov at gmail.com> --- There has been quite a few changes in the window you've mentioned. Thus to narrow it down further you can try - boot with "nouveau.config=MSI=0" to disable MSI interrupts(introduced in 3.12) If that does not help git bisect might be in order :) -- You are

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #6 from Emil Velikov <emil.l.velikov at gmail.com> --- Had a typo previously, the correct argument is nouveau.config=NvMSI=0 -- 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=69876 --- Comment #7 from Mike <michele.cane at gmail.com> --- Created attachment 87285 --> https://bugs.freedesktop.org/attachment.cgi?id=87285&action=edit dmesg output from nouveau.debug=trace -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #8 from Mike <michele.cane at gmail.com> --- (In reply to comment #6) > Had a typo previously, the correct argument is > nouveau.config=NvMSI=0 The behaviour remain the same with nouveau.config=NvMSI=0 -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #10 from Mike <michele.cane at gmail.com> --- If after xrandr --setprovideroffloadsink nouveau Intel i turn on the card with, for example, DRI_PRIME glxgers and then I xrandr --setprovideroutputsource nouveau Intel there is no freeze -- You are receiving this mail because: You are the assignee for the bug. --------------

https://bugs.freedesktop.org/show_bug.cgi?id=70464 Priority: medium Bug ID: 70464 Assignee: nouveau at lists.freedesktop.org Summary: [NVC3] runpm not working QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: michele.cane at gmail.com

https://bugs.freedesktop.org/show_bug.cgi?id=69876 Aaron Plattner <aplattner at nvidia.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|aplattner at nvidia.com |nouveau at lists.freedesktop.o | |rg

https://bugs.freedesktop.org/show_bug.cgi?id=93670 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Ilia Mirkin <imirkin at

----- Original Message ----- > From: "Ilia Mirkin" <imirkin at alum.mit.edu> > To: "David Airlie" <airlied at redhat.com> > Cc: "Ben Skeggs" <skeggsb at gmail.com>, "Ben Skeggs" <bskeggs at redhat.com>, nouveau at lists.freedesktop.org > Sent: Thursday, 20 March, 2014 9:49:47 AM > Subject: Re: [Nouveau] [PATCH] drm:

On Wed, Mar 19, 2014 at 7:45 PM, David Airlie <airlied at redhat.com> wrote: > >> On Thu, Mar 20, 2014 at 1:28 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> > There was a proliferation of duplicated checks for runpm == -1 && >> > optimus. Instead of continuing that tradition, get rid of all of them, >> > only doing the optimus

On Thu, Mar 20, 2014 at 1:28 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > There was a proliferation of duplicated checks for runpm == -1 && > optimus. Instead of continuing that tradition, get rid of all of them, > only doing the optimus computation once on load. > > This should hopefully fix secondary cards suspending and then being > unable to come back in

> On Thu, Mar 20, 2014 at 1:28 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > There was a proliferation of duplicated checks for runpm == -1 && > > optimus. Instead of continuing that tradition, get rid of all of them, > > only doing the optimus computation once on load. > > > > This should hopefully fix secondary cards suspending and then being

https://bugs.freedesktop.org/show_bug.cgi?id=70389 --- Comment #2 from Ilia Mirkin <imirkin at alum.mit.edu> --- Try updating your intel ddx -- nouveau is not responsible for the contents of the images it renders when in reverse-prime mode -- the primary gpu is (in your case, intel). -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

On Sat, Apr 5, 2014 at 7:53 AM, Claas Lorenz <cllorenz at uni-potsdam.de> wrote: > Hi, same for me. The screen does not freeze anymore and the boot Great! And that's without the nouveau.config=NvBios= stuff that you added as a workaround, right? > succeeds. But now I have this kernel message during boot (for the second > card): > > [ 24.382045]