similar to: [Bug 100406] New: [GP106M - Prime] Stall while waking card with DRI_PRIME=1 app

On Wed, Jan 11, 2017 at 4:48 AM, Sylvain Fabre <sylvain at lahiette.com> wrote: > Hi all, > > > > On my recent MSI Apache Pro laptop with Intel Skylake + GP106M Nvidia chip, > i am unable to use the external HDMI and DP outputs. The outputs are > available thru xrandr and can be activated, but the connected monitors > always show a black screen. > > > >

We've seen a number of power management and secboot issues with the Pascal-series mobile GPUs. Without a command line it is hard to debug remotely, but see, as one possible example: https://bugs.freedesktop.org/show_bug.cgi?id=100228 Can you try booting with a kernel command line that includes "nouveau.runpm=0" as a debugging step. On Mon, 17 Sep 2018 at 17:46, don fisher <hdf3

Hi all, On my recent MSI Apache Pro laptop with Intel Skylake + GP106M Nvidia chip, i am unable to use the external HDMI and DP outputs. The outputs are available thru xrandr and can be activated, but the connected monitors always show a black screen. Note that the integrated LCD is connected to the Skylage GPU, while the HDMI and DP outputs are connected to the NVIDIA GP106M GPU. The

Alienware 17 r5 also with same graphics (GP106M and Intel 3e9b) does boot from same disk. I look in hwinfo --gfxcard and it says both the Intel (on i915) and the Nvidia (nouveau) are both present. What command tells me which driver is being used? Thanks. Don

https://bugs.freedesktop.org/show_bug.cgi?id=94374 Bug ID: 94374 Summary: transparent window with DRI_PRIME=1, depending on size of used textures Product: Mesa Version: 11.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=107735 Bug ID: 107735 Summary: Xorg stops responding when running DRI_PRIME=1 glxgears Product: Mesa Version: 18.1 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=90632 Bug ID: 90632 Summary: DRI_PRIME=1 has no effect with GK106M Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=93934 Bug ID: 93934 Summary: DRI_PRIME=1: DeadIsland crashes when loading finish Product: Mesa Version: 11.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=100139 Bug ID: 100139 Summary: [DRI2][PRIME] nouveau driver cannot find any connected connector Product: Mesa Version: 10.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

I do not know how to debug this situation. Nothing appears in /var/log/messages. I miss the serial port:-( I executed a journalctl -r, and saw an error: kernel: nouveau 00001:01:00.0; Refused to change power state, currently in D3 The last message before reboot was: kernel: watchdog: Bug: soft lockup - CPU#0 stuck for 22s! [ntpd:3265] I have a pair of these Alienware 13 laptops, and would be

On Thu, Jan 12, 2017 at 3:51 AM, Sylvain Fabre <sylvain at lahiette.com> wrote: > xrand > > Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 > eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y > axis) 344mm x 194mm > 1920x1080 60.02*+ 47.99 > 1400x1050 59.98 > 1280x1024 60.02 > 1280x960 60.00

On Fri, Jan 13, 2017 at 10:11 AM, Sylvain Fabre <sylvain at lahiette.com> wrote: > xrandr --setprovideroutputsource 1 0 seems to do nothing, either with a > monitor connected to HDMI-1 or not. The second monitor is detected and > available in the screen configuration tool of KDE, but it remains black, no > window, nothing. > > With a monitor conected in HDMI-1, here are the

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. --------------

Hi, While trying PRIME, I got a lockdep warning after exiting glxgears. Is it harmful? The command was: DRI_PRIME=1 glxgears Offload provider is a GT425M (NVC0), output sink is an Intel i5-460M. Kind regards, Peter dmesg: ============================================= [ INFO: possible recursive locking detected ] 3.15.0-rc8-custom-00058-gd2cfd31 #1 Tainted: G O

https://bugs.freedesktop.org/show_bug.cgi?id=96390 Bug ID: 96390 Summary: [GK208] DISP failure while using PRIME offloading Product: xorg Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

> > No, that line is actually expected (just means accel won't work, since > NVIDIA hw now requires signed firmware, but they won't release the > ctxsw fw). Are you absolutely sure that you're seeing the outputs in > xrandr? Could you provide the output of xrandr as well as an Xorg log? > > Thanks, > > -ilia Many thanks for you help. All data below :

https://bugs.freedesktop.org/show_bug.cgi?id=93201 Chris Wilson <chris at chris-wilson.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Driver/intel |Driver/nouveau Assignee|chris at chris-wilson.co.uk |nouveau at lists.freedesktop.o

https://bugs.freedesktop.org/show_bug.cgi?id=93201 --- Comment #6 from Marcos Souza <marcos.souza.org at gmail.com> --- (In reply to Chris Wilson from comment #5) > I'm going to assume the DRICloseScreen in the middle of the stack is just > the unwinder getting confused and so this looks like a nouveau bug and not a > core DRI2 bug. So, in this case, there is a start point to

https://bugs.freedesktop.org/show_bug.cgi?id=93201 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #7 from Martin Peres

https://bugs.freedesktop.org/show_bug.cgi?id=88514 Bug ID: 88514 Summary: X segfaults when using prime offloading to nouveau card Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: