Bug 1226240 - Server crash when pluging screen to DP port
Summary: Server crash when pluging screen to DP port
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 22
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-29 09:35 UTC by Mathieu Chouquet-Stringer
Modified: 2016-07-19 19:09 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 19:09:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lspci (2.22 KB, text/plain)
2015-05-29 11:17 UTC, Mathieu Chouquet-Stringer
no flags Details
Xorg.0.log (48.52 KB, text/plain)
2015-05-29 11:18 UTC, Mathieu Chouquet-Stringer
no flags Details

Description Mathieu Chouquet-Stringer 2015-05-29 09:35:59 UTC
Description of problem:

I have a Lenovo T530 with a docking station. The laptop has the dreaded optimus setup (with both intel and nvidia chips).

Sadly it seems the external DP ports (regular not mini) on the docking station can only be used through the nvidia chip (found about that here http://www.thinkwiki.org/wiki/DisplayPort#Problems and trial/error seem to show it's true)...

So the setup is as follow: X server started with only the internal display.

Then I connect an external monitor, I can find it's being detected. If I try to enable it in the gnome interface, it immediately kills the X server (with a segfault).

I have the same behavior if I boot up the laptop with the external screen connected: X crashes over and over while trying to start the GDM session.


Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg 1.17.1-12.fc22

How reproducible: always


Steps to Reproduce:
1. start X server
2. connect external screen using displayport
3. enable it
4. boom

Actual results:

Please find the gdb backtrace output below, let me know if you need anything else.

Note the whole abrt-dump-xorg thing doesn't work anymore because the log file isn't /var/log/Xorg.${TTYNUMBER}.log anymore but something like $HOME/.local/share/xorg/Xorg.${TTYNUMBER}.log

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
#0  0x0000000000000000 in ?? ()
No symbol table info available.
#1  0x000000000045692f in PixmapShareToSlave (pixmap=pixmap@entry=0x24f4b70, slave=0x177e360) at pixmap.c:157
        spix = 0x2607880
        ret = <optimized out>
        handle = 0x3c
        master = <optimized out>
        depth = 24
#2  0x00000000004fb79f in rrCreateSharedPixmap (y=0, x=1920, height=1200, width=1920, crtc=0x1789980) at rrcrtc.c:423
        mpix = 0x24f4b70
        spix = <optimized out>
        master = 0x17b0170
        ret = <optimized out>
        depth = 24
        mscreenpix = 0x25d95e0
        protopix = <optimized out>
#3  RRCrtcSet (crtc=0x1789980, mode=0x2214260, x=1920, y=0, rotation=rotation@entry=1, numOutputs=numOutputs@entry=1, outputs=0x25d9660) at rrcrtc.c:567
        master = 0x17b0170
        width = 1920
        height = 1200
        pScreen = 0x177e360
        ret = <optimized out>
        crtcChanged = <optimized out>
        o = <optimized out>
#4  0x00000000004fc5b3 in ProcRRSetCrtcConfig (client=0x212d2c0) at rrcrtc.c:1173
        stuff = <optimized out>
        rep = {type = 0 '\000', status = 0 '\000', sequenceNumber = 0, length = 0, newTimestamp = 0, pad1 = 0, pad2 = 0, pad3 = 0, pad4 = 0, pad5 = 0}
        pScreen = <optimized out>
        pScrPriv = 0x1789830
        crtc = 0x1789980
        mode = 0x2214260
        numOutputs = <optimized out>
        outputs = <optimized out>
        time = <optimized out>
        rotation = 1
        ret = <optimized out>
        i = <optimized out>
        j = <optimized out>
        status = <optimized out>
#5  0x000000000043a1bf in Dispatch () at dispatch.c:432
        clientReady = 0x2141bf0
        result = <optimized out>
        client = 0x212d2c0
        nready = 0
        icheck = 0x82f430 <checkForInput>
        start_tick = 400
#6  0x000000000043e2fb in dix_main (argc=14, argv=0x7ffee4b4d168, envp=<optimized out>) at main.c:298
        i = <optimized out>
        alwaysCheckForInput = {0, 1}
#7  0x00007f1e7d89c790 in __libc_start_main (main=0x4286f0 <main>, argc=14, argv=0x7ffee4b4d168, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffee4b4d158) at libc-start.c:289
        result = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 2182834629096666325, 4359936, 140732735476064, 0, 0, -2182216830108928811, -2272621123817802539}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x5a6af0 <__libc_csu_init>, 
              0x7ffee4b4d168}, data = {prev = 0x0, cleanup = 0x0, canceltype = 5925616}}}
        not_first_call = <optimized out>
#8  0x0000000000428729 in _start ()
No symbol table info available.
[Thread 0x7f1e7681c700 (LWP 9459) exited]
[Thread 0x7f1e7701d700 (LWP 9458) exited]
[Thread 0x7f1e7fe899c0 (LWP 9412) exited]
[Inferior 1 (process 9412) exited with code 01]

Comment 1 Mathieu Chouquet-Stringer 2015-05-29 09:41:31 UTC
Note I only use the intel and nouveau driver, I'll upload the X log output in a few.

Comment 2 Mathieu Chouquet-Stringer 2015-05-29 11:17:14 UTC
Created attachment 1031948 [details]
lspci

Comment 3 Mathieu Chouquet-Stringer 2015-05-29 11:18:06 UTC
Created attachment 1031951 [details]
Xorg.0.log

Comment 4 Mathieu Chouquet-Stringer 2015-05-29 11:55:47 UTC
Note this is exactly the same with the new xorg-x11-drv-intel-2.99.917-9.20150520.fc22.x86_64

Comment 5 Mathieu Chouquet-Stringer 2015-06-01 07:54:55 UTC
I reported the bug upstream and they came up with a working patch, patch that can be applied to the current package.

https://bugs.freedesktop.org/show_bug.cgi?id=90771#c2

Comment 6 Mathieu Chouquet-Stringer 2015-06-07 16:24:45 UTC
Patch still not present in xorg-x11-server-1.17.1-14.fc22.src.rpm

Comment 7 Fedora End Of Life 2016-07-19 19:09:31 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.