Nouveau - Nov 2014 - [Bug 86164] New: Dual screen causes KDE crash on NV50 (NV98) in nouveau (bisected)

https://bugs.freedesktop.org/show_bug.cgi?id=86164

            Bug ID: 86164
           Summary: Dual screen causes KDE crash on NV50 (NV98) in nouveau
                    (bisected)
           Product: xorg
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: maris.nartiss at gmail.com
        QA Contact: xorg-team at lists.x.org

Created attachment 109296
  --> https://bugs.freedesktop.org/attachment.cgi?id=109296&action=edit
A Xorg log file of failing session

Starting with "[86024ceef015ffe31a204cc5bc6c326a19363ff1] glamor: initial
support (no dri)" is not possible to configure a secondary monitor while
running KDE 4.14.2. 

Steps to reproduce:
Version A:
 * while a KDE session is open, plug in a secondary monitor
 * use KDE display configuration tool to enable second monitor
 * X11 server gets restarted -> KDM window appears

Version B:
 * start system with a secondary monitor attached
 * observe how system is running in a "clone" mode (there is output on
secondary monitor)
 * log in in KDM
 * observe how X11 gets restarted -> KDM window appears

Solution - use any revision before 86024ceef0

Unfortunately log files are empty - there are no meaninful messages that could
shead a light on the issue. No crash is recorded, xorgsession-errors are just
indicating on IO error while connecting to X11;

There is some issue with EDID, although KDE monitor configuration displays
correct information. dmesg snip:
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/kernel-3.17.2
root=/dev/sda2 ro nouveau.noaccel=1 resume=/dev/sda6
[   13.310327] nouveau 0000:01:00.0: irq 36 for MSI/MSI-X
[   14.481036] fbcon: nouveaufb (fb0) is primary device
[   14.818215] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[   14.818217] nouveau 0000:01:00.0: registered panic notifier
[   14.832075] [drm] Initialized nouveau 1.2.0 20120801 for 0000:01:00.0 on
minor 0
[  103.530600] Raw EDID:
[  103.530603]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  103.530605]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  103.530605]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  103.530606]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  103.530607]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  103.530608]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  103.530609]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  103.530610]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  103.530614] nouveau 0000:01:00.0: VGA-1: EDID block 0 invalid.
[  103.530617] nouveau E[     DRM] DDC responded, but no EDID for VGA-1


git bisect start
# bad: [3fb97d78202213c1221a1d3ad8a5cebda78fdf44] fix null pointer deref
git bisect bad 3fb97d78202213c1221a1d3ad8a5cebda78fdf44
# good: [480f0998ffed6d9a5c6656dba75182f00fd88a1b] bump to 1.0.10 for release
git bisect good 480f0998ffed6d9a5c6656dba75182f00fd88a1b
# bad: [f0fa8313714c2a5b16e784b257b5ff79da3a443b] dri2: Enable sync of
bufferswaps to Vblank by default.
git bisect bad f0fa8313714c2a5b16e784b257b5ff79da3a443b
# bad: [81148bb1dbc7007c021c59411d56cb31cfc74ef2] glamor: provide dri3 support
when enabled
git bisect bad 81148bb1dbc7007c021c59411d56cb31cfc74ef2
# good: [b24cae0bf5db6ece21439d4c6ff3668aed4c78d6] dri2: move "is
supported"
checks out of nv_driver.c
git bisect good b24cae0bf5db6ece21439d4c6ff3668aed4c78d6
# good: [4b138ab18f58c6d459e21dc319615f536c8e69c8] merge nv_dma.c into
nv_accel_common.c
git bisect good 4b138ab18f58c6d459e21dc319615f536c8e69c8
# good: [fd0ce8839f307693d86c7602dd926ce79e6b777d] add support for maxwell,
minus Xv/renderaccel
git bisect good fd0ce8839f307693d86c7602dd926ce79e6b777d
# bad: [86024ceef015ffe31a204cc5bc6c326a19363ff1] glamor: initial support (no
dri)
git bisect bad 86024ceef015ffe31a204cc5bc6c326a19363ff1
# first bad commit: [86024ceef015ffe31a204cc5bc6c326a19363ff1] glamor: initial
support (no dri)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141111/5e4bf121/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86164

--- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> ---
While it shouldn't cause crashes, I suspect that removing

nouveau.noaccel=1

should resolve this issue. Why are you booting with that?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141111/98df8191/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86164

Maris Nartiss <maris.nartiss at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Dual screen causes KDE      |Screen resize causes crash
                   |crash on NV50 (NV98) in     |on NV50 (NV98) in nouveau
                   |nouveau (bisected)          |(bisected)

--- Comment #2 from Maris Nartiss <maris.nartiss at gmail.com> ---
(In reply to Ilia Mirkin from comment #1)
> While it shouldn't cause crashes, I suspect that removing
> 
> nouveau.noaccel=1
> 
> should resolve this issue. Why are you booting with that?
Sorry, my analysis was incomplete. Today I tested with bare bones X session
(xinit running xterm) without a secondary output - it still fails on screen
resize issued with "xrandr -s 1024x768". Attaching a secondary output
was just
triggering screen size change.

If screen size change is triggered from xinit, it gets stuck with a black,
empty screen. Attempts to use get to VT (ctrl+alt+f1) are failing, I never have
been able to get killing X server option to work (whoever had that
"bright"
idea to remove ctrl+alt+backspace option), and simple reboot (ctrl+alt+del)
doesn't work. Still system (sometimes) reacts on power button, although it
can't finish shutdown - there is a disk activity, but it fails to power off.

Changing nouveau.noaccel=0 with current git master makes this bug to disappear
- "xrandr -s" calls are not failing any more. Still some graphical
corruption
is observable (invisible parts of web page in Firefox are randomly appearing
while typing in FF this report) - a different bug and I have no idea how to
reproduce it. The original reason for disabling acceleration was (IIRC)
inability to suspend system more than once and to play any video after first
resume. Don't remember exact bug #, but that's a different story, as
"xrandr
-s" calls shouldn't crash X also without acceleration enabled.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141112/e83559c8/attachment-0001.html>

Hi,
I have a GTX 770 (NVE4)
back on 3.16.X kernel i was able to reclock my gpu using 
/sys/class/drm/card0/device/pstate 
but now on 3.18 (rc4) all proper reclocking support is gone from pstate.
how should i be able to reclock again my GPU?


cheers
Lucas.

Someone complained about pstate being in sysfs, and we haven't gotten
a chance to move it to debugfs yet, so it's behind a module parameter
(nouveau.pstate=1 iirc) for now. It'll probably move to debugfs at
some point.

On Thu, Nov 13, 2014 at 12:35 PM, Lucas Francesco
<lucas.gesteira at escolartedeviver.com.br> wrote:
> Hi,
> I have a GTX 770 (NVE4)
> back on 3.16.X kernel i was able to reclock my gpu using
> /sys/class/drm/card0/device/pstate
> but now on 3.18 (rc4) all proper reclocking support is gone from pstate.
> how should i be able to reclock again my GPU?
>
>
> cheers
> Lucas.
>
> _______________________________________________
> Nouveau mailing list
> Nouveau at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=86164

Martin Peres <martin.peres at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |MOVED
             Status|NEW                         |RESOLVED

--- Comment #3 from Martin Peres <martin.peres at free.fr> ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/150.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20191204/cf0a6e09/attachment.html>