All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 104344] New: Display Adapter Chain, Cable Disconnect causes Nouveau crash
Date: Wed, 20 Dec 2017 05:52:17 +0000	[thread overview]
Message-ID: <bug-104344-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2678 bytes --]

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

            Bug ID: 104344
           Summary: Display Adapter Chain, Cable Disconnect causes Nouveau
                    crash
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: mbazzinotti-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 136308
  --> https://bugs.freedesktop.org/attachment.cgi?id=136308&action=edit
collation of syslog grep'd for "nouveau|drm"; includes trace. there was no
pertinent log info right before the trace occurred.

While experimenting with physical connections to avert Flicker Bug 88272
(https://bugs.freedesktop.org/show_bug.cgi?id=88272)

I found myself using a mini DisplayPort(mDP) adapter which has 3 outputs
(HDMI, DVI, and DP), with its DP output connected to a second DP->DVI adapter.

Let's call the first adapter A, and the 2nd adapter B. The connections are:


-------  mDP  ---  DP  --- DVI --------- 
Laptop |-----| A |----| B |---| Monitor |
-------       ---      ---     ---------


While connected, display appeared "normal" as per Bug 88272 screen flicker.
When
I unplugged the DVI cable from adapter B, this trace appeared in the dmesg
attachment. Dmesg Output before the trace was not relevant. This issue can be
reproduced again and again by reconnecting and disconnecting the cable.

This does not crash X. The desktop appears to run just fine, even during the
nouveau crash IIRC. If I was not watching dmesg, I may not have even noticed.

The problem does not happen if unplugging the root adapter from the laptop. I
have not tried unplugging the 2nd adapter to see what happens in that case.

Note: When adapter A is plugged via DVI to monitor directly, unplugging the DVI
cable does not cause a crash; no call stack is outputted to dmesg in this case.

---------
Hardware |
---------
Macbook Pro 5,4 15" mid-2009
Nvidia GeForce 9400m
mini DisplayPort -> "Gigaware" DVI/HDMI/Displayport adapter -> HP DP>DVI
adapter
Dell LCD Monitor model E2011Hc

--------
Software|
--------
Gentoo Linux 4.12.12. 
x11-base/xorg-server-1.19.5
x11-drivers/xf86-video-nouveau-1.0.15
i3wm
No compositor

kernel command line: ro root=PARTUUID=xxxxxxxx net.ifnames=0

-----

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4937 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2017-12-20  5:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20  5:52 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-104344-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-12-21 20:46   ` [Bug 104344] Display Adapter Chain, Cable Disconnect causes Nouveau trace bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-21 21:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-104344-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.