All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91333] Connecting second of two monitors to a Lenovo W520 causes displays to go crazy
Date: Tue, 14 Jul 2015 17:00:18 +0000	[thread overview]
Message-ID: <bug-91333-8800-VVD0Q3kRLi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91333-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #9 from Corey Ashford <cjashfor-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> ---
(In reply to Mark Cave-Ayland from comment #8)
> Apologies for jumping in on another bug report, however this sounds exactly
> like the problem I've been struggling with for years on my Lenovo T420s:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=56615
> 
> I see the same symptoms in that the kernel "hangs" with an external
> DisplayPort connected in discrete mode when trying to use the internal LVDS
> with the external monitor. It seems the message I get in the kernel log is
> similar too:
> 
> nouveau E[   PDISP][0000:01:00.0] chid 1 mthd 0x0080 data 0x00000000
> 0x00005080 0x0000000

Yeah, it does seem similar.  However, in my case, a single external monitor
along with the internal LVDS works fine.

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

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

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

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

  parent reply	other threads:[~2015-07-14 17:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  1:46 [Bug 91333] New: Connecting second of two monitors to a Lenovo W520 causes displays to go crazy bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-91333-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-07-14  1:52   ` [Bug 91333] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14  3:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14  3:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14  3:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14  4:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14  4:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14  4:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14  8:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14 17:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-07-14 17:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15  0:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15  2:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15  2:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15  6:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15  8:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-18  8:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:01   ` 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-91333-8800-VVD0Q3kRLi@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.