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 64774] nouveau GF108 kernel crash in optimus mode when enabling external display output
Date: Fri, 19 Jul 2013 14:30:02 +0000	[thread overview]
Message-ID: <bug-64774-8800-pwICfrQ7CF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64774-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #17 from Pasi Kärkkäinen <pasik-X3B1VOXEql0@public.gmane.org> ---

Oh, one more interesting piece of information.. 

If I boot (power-on) the laptop *without* DVI cable connected, the nouveau
connectors will show up in 'xrandr' output as DP-1, DP-2 and DP-3. 

Now If i boot (power-on) the laptop *with* DVI cable connected, the nouveau
connectors will *NOT* show up in 'xrandr' most of the times, but during that
maybe one time out of ten when they do show up in 'xrandr', they're actually
called DisplayPort-0, DisplayPort-1 and DisplayPort-2. 

I wonder why that difference.. and if it's related to the issue I'm having or
not. I'm only able to hit the nouveau kernel crash when the connectors are
called DisplayPort-X, it seems. When the connectors are called DP-X, I'm not
able to crash the kernel.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2013-07-19 14:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 20:54 [Bug 64774] New: nouveau GF108 kernel crash in optimus mode when enabling external display output bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-64774-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-05-19 20:55   ` [Bug 64774] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 20:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 20:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 21:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 21:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 12:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 14:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 14:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 14:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-07-21 10:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 18:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 20:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 16:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 17:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 17:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-01 16:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-02  0:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-02  1:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-06 16:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8: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-64774-8800-pwICfrQ7CF@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.