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 16233] New: [Randr12] Server crash when detecting DVI output change
Date: Wed,  4 Jun 2008 14:51:00 -0700 (PDT)	[thread overview]
Message-ID: <bug-16233-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=16233

           Summary: [Randr12] Server crash when detecting DVI output change
           Product: xorg
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Keywords: regression
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: chalserogers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=16916)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=16916)
Xorg log containing crash after running 'xrandr'

I have two DVI devices: a LCD panel with single channel DVI interface and a TV
connected over a dual-channel DVI->HDMI.  Nouveau kills X when swapping between
them in the following way:
1) Connect LCD panel to DVI port.
2) xrandr --auto to bring it up.
3) xrandr --output DVI-D-0 --off to bring it down
4) Disconnect LCD, plug DVI->HDMI cable into same DVI port
5) Run xrandr <-- Crash here.

This is symmetric, in that TV->LCD crashes in the same way that LCD->TV does.

I've run a git-bisect, and the offending commit is:
cdae2e26cc432ba572f92522f1b3454264d38f43 is first bad commit
commit cdae2e26cc432ba572f92522f1b3454264d38f43
Author: Maarten Maathuis <madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date:   Fri Jan 25 00:10:08 2008 +0100

    randr12: Rework native modes for TMDS.

    - Choose a preferred ddc mode when available, otherwise the one with the
highest refresh.
    - Fall back on cvt modes, only when needed.

:040000 040000 497af7e1199ee5079d38ab8dd668c1612230dfb7
78929b01e4e079417a26e25b64788c5c75cf3878 M      src


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2008-06-04 21:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 21:51 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-16233-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-06-04 21:51   ` [Bug 16233] [Randr12] Server crash when detecting DVI output change bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-04 21:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-04 21:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-04 21:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-25 18:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-26 12:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-26 13:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-29  2:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-29 12:53   ` 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-16233-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.