From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 54681] Connecting TV to second DVI port of 9600GT card causes GPU lockup and Xorg crash
Date: Wed, 14 Nov 2012 03:03:11 +0000 [thread overview]
Message-ID: <bug-54681-8800-5VeihxKyPY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-54681-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1600 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=54681
--- Comment #1 from Robert Hancock <hancockrwd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
This bug is still occurring with kernel-3.6.6-1.fc17.x86_64 and
xorg-x11-drv-nouveau-0.0.16-37.20120306gitf5d1cd2.fc17.x86_64. I also get
errors like this sometimes when the crash occurs:
[Nov 13 19:01:29 newcastle kernel: [ 41.878583] [drm] nouveau 0000:01:00.0:
EvoCh 2 Mthd 0x0080 Data 0x00000000 (0x000b 0x05)
Nov 13 19:01:30 newcastle kernel: [ 42.458475] [drm] nouveau 0000:01:00.0:
EvoCh 2 Mthd 0x0080 Data 0x00000000 (0x100b 0x05)
Nov 13 19:01:36 newcastle kernel: [ 48.447320] [drm] nouveau 0000:01:00.0:
EvoCh 2 Mthd 0x0080 Data 0x00000000 (0x100b 0x05)
Nov 13 19:01:47 newcastle kernel: [ 59.468318] [drm] nouveau 0000:01:00.0:
Failed to idle channel 2.
Nov 13 19:01:50 newcastle kernel: [ 62.533759] [drm] nouveau 0000:01:00.0:
Failed to idle channel 4.
Nov 13 19:01:59 newcastle kernel: [ 68.933395] [drm] nouveau 0000:01:00.0:
EvoCh 2 Mthd 0x0080 Data 0x00000000 (0x100b 0x05)
I realized that I had my main monitor connected to what the driver calls
DVI-I-2 and the TV connected to DVI-I-1. If I reverse the connections to put
the TV on port 2 instead, it works a bit better in that I can
connect/disconnect the TV and extend the display onto it without things blowing
up. But doing things in the Display app like disabling the main monitor and
using just the TV, then disabling the TV and turning the monitor back on, will
trigger such crashes again.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2408 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2012-11-14 3:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 5:31 [Bug 54681] New: Connecting TV to second DVI port of 9600GT card causes GPU lockup and Xorg crash bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-54681-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-11-14 3:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-08-25 4:37 ` [Bug 54681] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 4:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 4:48 ` 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-54681-8800-5VeihxKyPY@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox